Call for testing of colocated branch support in bzr.dev

[Jelmer Vernooij]

On Mon, Feb 20, 2012 at 11:12:49PM +1100, Andrew Bennetts wrote:
> John Arbash Meinel wrote:
> [...]
> > I think the original problem was Robert didn't want to create a branch
> > at 'tip' revision, when the repo didn't have the data yet. Which is
> > fair enough, though I think creating the Branch at NULL_REVISION, and
> > then updating it to 'tip' when the fetch finishes is probably a good
> > way to go.
> > 
> > It would really simplify the fetch code, so that we wouldn't have
> > separate fetch logic for first creation vs updating.
> 
> It could perhaps also be a (small) step towards supporting interruptible
> pushes, where the Branch's last revision is periodically updated to what
> we have pushed so far.  Perhaps that isn't the behaviour we'd like,
> although it seems intuitive: if you break the lock, you get a
> branch that is part of the way to the revision that you were trying to
> push.
> 
> Anyway, +1 on just creating a Branch at NULL_REVISION.  It certainly
> won't be a worse experience than what happens now.
I think this would be a good idea too.

I'm not sure about periodically updating the branch during fetch, but
at least creating an empty branch with the right stacking data would
be nice.

Cheers,

Jelmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20120220/90d88bc9/attachment.pgp>