[MERGE] bundles use parent location as default base

John Arbash Meinel john at arbash-meinel.com
Sun Jun 18 06:02:59 BST 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Bentley wrote:
> Hi all,
> 
> Here's a patch to make the bundle command default to using the parent
> branch as its base branch.
> 
> This means that 'branch; commit; commit; bundle' will Do The Right
> Thing.  (The current behavior is to generate a bundle against the first
> commit, which means that the resulting bundle cannot be applied to the
> original branch.)
> 
> I recognise that the parent is not necessarily the best branch to use.
> I would like to add 'Branch.get_submit_branch', and use that, but I
> should wait until I've landed some more config changes.  Eventually,
> there should be a 'bundle --remember' option, but I'd like to save that
> until Branch.set_submit_branch has been implemented.
> 
> Aaron

While 'SubmitByMail' is supposed to take care of the best destination,
at present 'parent' is better than nothing.
It won't always be right, but it will be less wrong than what we have now.

And from what I can tell, the current behavior can be gotten by using:
bzr bundle .

So +1 from me.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFElN6DJdeBCYSNAAMRAlYuAJ9MFC0sC5EIHlL7dvN9clCOrbF2AwCfVzNS
qRn0gBPst+1aVPpTjA+vgXw=
=nkbN
-----END PGP SIGNATURE-----




More information about the bazaar mailing list