Committing multiple branches to Launchpad

[Stephen M. Webb]

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

On 15-09-30 11:03 AM, Ted Cox wrote:
> Doug, Gunnar, and I saw some behavior with Launchpad where changes from previous merge proposals show up in new
> merge proposals.
> 
> Here's what I was doing:
> 
> 1. Edit file1.xml 2. bzr commit --fixes... 3. bzr push lp:~ted-m-cox/serverguide/branch1 4. Submit merge proposal
> for branch 1 5. Edit file2.xml 6. bzr commit --fixes... 7. bzr push lp:~ted-m-cox/serverguide/branch2 8. Submit
> merge proposal for branch2
> 
> On Launchpad, changes from branch1 would then show up in the merge proposal for branch2. If I'm working on multiple
> bug fixes, should I commit and push in a different way? Maybe make several small commits and then push everything
> to one branch?

You should either set your second MP to have the first as a prerequisite, or else start them both from a pristine
checkout instead of piggybackinmg them.


- -- 
Stephen M. Webb  <stephen at ubuntu.com>
https://launchpad.net/~bregma
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlYL+uEACgkQTLRKqWcl7vNg8gCeK2Sz/nW2ZiDdKZ1ujHj5t0J/
8owAoLKxUpUbPW86QJWG2x6NFaL9NGSA
=omYg
-----END PGP SIGNATURE-----