Committing multiple branches to Launchpad

[Wesley Schwengle]

I'm not sure how launchpad deals with it (aka I don't know the LP commands to do it), but looking at your workflow you don't branch from master, you continue to work on branch1. Branch 2 therefore contains commits intended for another branch.

In git I would do something like

git co -t upstream/master -b branch1
# hack hack hack
git commit
git push origin branch1

And the same for branch2. 

This might be useful:
http://nvie.com/posts/a-successful-git-branching-model/

Cheers, 
Wesley

On 30 September 2015 11:03:41 GMT-04:00, Ted Cox <ted.m.cox at gmail.com> 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!
>
>-- 
>ubuntu-doc mailing list
>ubuntu-doc at lists.ubuntu.com
>https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-doc/attachments/20150930/5afa91ad/attachment.html>