Committing multiple branches to Launchpad

[Peter Matulis]

On 09/30/2015 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?
> 
> Thanks!
> 

I keep updated master branches (for 12.04, trunk, etc) locally and from
them a separate branch is created for each thing I work on. This results
in a filesystem layout that provides meaning to me, especially when the
branches are named intelligently.

pM