Probably bug: branch dirstate branch to knitpack repo does not upgrade branch to dirstate-tags

Robert Collins robertc at robertcollins.net
Mon Nov 12 18:28:50 GMT 2007


On Mon, 2007-11-12 at 13:21 -0500, Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Robert Collins wrote:
> 
> >> It seems like the "detect format name" code needs to be updated for packs. It
> >> does seem like a bug to me. Since it is still marked as an experimental format,
> >> it doesn't seem critical to release 0.92.1.
> > 
> > Hmm, this seems to behave as intended:
> 
> To me, it raises the question: "is this still how we want to do this"?
> Ideally, we have separation between repo format, branch format and tree
> format, but do we really want people using random combinations of them?
>  It seems like an additional burden with no clear benefit.

I think this is a good question. The original design was intended to
prevent accidentally exposing features the origin branch's user could
not use via commits to target branch.

Repositories were special cased because they require an explicit step to
setup, so if you have e.g. a pack repository its a deliberate step
rather than bzr spuriously making it hard to collaborate.

I think this is actually working rather well, but I can certainly see
adding something that says 'when you branch from a tagless branch make
it a tag capable branch'. I definitely don't want to see 'branching from
any branch makes a default format branch'.

-Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20071113/2f9d41ce/attachment.pgp 


More information about the bazaar mailing list