Nested tree support - current status
Joshua Judson Rosen
rozzin at hackerposse.com
Tue Oct 22 21:22:35 UTC 2019
On 10/14/19 12:49 PM, Jelmer Vernooij wrote:
> So we're making steady progress on nested tree support.
>
> The bulk of work was actually in getting rid in file-id based lookups, since they can potentially involve opening all subtrees. These are now mostly gone.
Wait, what? I liked file-IDs.... They are (were?) bzr's way of not throwing away
the information that I explicitly gave it when I renamed files....
That git immediately throws away info about renames thinking that it knows
better than I do about what I did is one of the sore points that has kept me using bzr
all these years.
We're not actually losing proper rename-tracking as a feature in brz, are we?
(sorry if I'm off-base; I haven't been able to follow along very closely...)
> The next steps are:
>
> * Update Tree.list_files (mp out for review)
> * Update Tree.iter_entries_by_dir (mp prepared)
> * Update Tree.iter_changes (mp in progress)
> * Update Tree.get_* to accept nested paths (mp mostly done, needs tests)
>
> And then finally, updating commands:
>
> * add --no-recurse-nested flag to diff, log, ls, status (changes done, needs tests)
> * add --no-recurse-nested flag to branch/pull/push
>
> And eventually:
>
> * Support moving files between nested trees
> * Allow rename detection across trees
>
> Jelmer
--
Connect with me on the GNU social network! <https://status.hackerposse.com/rozzin>
Not on the network? Ask me for more info!
More information about the bazaar
mailing list