Must respecify --no-qa on each submission attempt
Bug #722155 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar PQM Plugin |
Triaged
|
Low
|
Unassigned | ||
| Launchpad Developer Utilities |
Triaged
|
Low
|
Unassigned | ||
Bug Description
If you 'ec2 land' a branch with --no-qa, and that branch fails to land for some reason, then when you try to land the branch again, you have to specify --no-qa again, even though the commit message on the merge proposal already has [no-qa] in it.
| summary: |
- Must respecify --no-qa on every run of ec2 + Must respecify --no-qa on each submission attempt |
Revision history for this message
| Aaron Bentley (abentley) wrote | #1 |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #2 |
| tags: |
added: ec2land ec2test removed: ec2 |
| affects: | launchpad → lp-dev-utils |
| Changed in bzr-pqm: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
Using trunk r79 and later with a commit message containing launchpad PQM tags is sub-optimal anyway, because it will prepend its own copy of those tags. (lp-land itself no longer alters merge proposal commit messages, so it does not expect those tags to be present.)