lp:~jameinel/bzr/lazy_revno

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

3530. By John A Meinel on 2009-01-20

Expose get_lazy_revno_mapper() as part of Branch.

3529. By John A Meinel on 2009-01-20

Revert the is_ghost workaround, because it was incorrect anyway.

3528. By John A Meinel on 2009-01-20

Merge bzr.dev 3948

3527. By John A Meinel on 2008-08-08

Merge bzr.dev 3616, including fixes for merge_sort

3526. By John A Meinel on 2008-08-07

Reproduce bzr.dev's numbering logic by filtering ghosts. (breaks tests)

3525. By John A Meinel on 2008-08-07

Turn ghosts into just another shortcut to NULL_REVISION

3524. By John A Meinel on 2008-08-07

Injecting a 'dummy' revision fixes both problems, not sure if it is 100% correct

3523. By John A Meinel on 2008-08-07

We need one more bit to test the other part.
If we remove only parents that are not in the ancestry, it causes
the staging branch to appear to be descended from the feature branch
(its left-hand parent is removed, so the feature becomes the parent)
This only shows up when numbering another child, which should be
preserved on the same 'branch'.

3522. By John A Meinel on 2008-08-07

Add a test which shows a failing numbering.
Basically, with a staging branch, its base is old enough that we
filter it out when numbering.
We can't just remove the left-hand parent, because that would make it look
like we *descended* from the feature branch (and give wrong numberings)
But if we filter out *all* parents, then it looks like the feature was not merged.

3521. By John A Meinel on 2008-08-07

Change _propagate_descended_from to do what I thought I was doing :)
I thought I was doing a depth-first, but it turned out I was just stepping breadth-wise.
Doesn't change the problems, but should be a small improvement to prevent re-walking
the same nodes repeatedly.