Merge lp:~shawn111/bzr/lp_propose_message into lp:bzr
Proposed by
Shawn Wang
Status: | Merged |
---|---|
Approved by: | Richard Wilbur |
Approved revision: | no longer in the source branch. |
Merged at revision: | 6619 |
Proposed branch: | lp:~shawn111/bzr/lp_propose_message |
Merge into: | lp:bzr |
Diff against target: |
12 lines (+2/-0) 1 file modified
bzrlib/plugins/launchpad/lp_propose.py (+2/-0) |
To merge this branch: | bzr merge lp:~shawn111/bzr/lp_propose_message |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Richard Wilbur | Approve | ||
Vincent Ladeuil | Pending | ||
Review via email: mp+258742@code.launchpad.net |
Commit message
Use initial_comment as commit_message for lp_propose.(Shawn Wang)
Description of the change
use initial_comment as commit_message for lp_propose
To post a comment you must log in.
I was interested to see your branch but when I visit the merge request, even though you filed it 9 hours ago, it still says "Updating diff... An updated diff will be available in a few minutes. Reload to see the changes." I reload with no change to what is displayed.
I've seen this problem occur in the past when someone created a stacked branch of lp:bzr.
Here's the recipe I use:
bzr branch lp:bzr [local_ branch_ name_if_ not_bzr] branch_ name_if_ not_bzr}
cd {bzr|local_
[edit the file(s) with your favorite editor]
./bzr selftest # To make sure you didn't break anything.
bzr commit -m 'Describe your changes.'
bzr push lp:~shawn111/bzr/lp_propose_message
Then visit here:
https:/ /code.launchpad .net/~shawn111/ bzr/lp_ propose_ message/ +register- merge
Fill out the form and submit.