Must respecify --no-qa on each submission attempt

Bug #722155 reported by Jonathan Lange on 2011-02-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar PQM Plugin
Low
Unassigned
Launchpad Developer Utilities
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.

Jonathan Lange (jml) on 2011-02-20
summary: - Must respecify --no-qa on every run of ec2
+ Must respecify --no-qa on each submission attempt
Aaron Bentley (abentley) wrote :

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.)

Julian Edwards (julian-edwards) wrote :

I reported bug 715832 which is almost the exact opposite of this bug.

Jonathan Lange (jml) on 2011-03-09
tags: added: ec2land ec2test
removed: ec2
Aaron Bentley (abentley) on 2012-03-08
affects: launchpad → lp-dev-utils
Jelmer Vernooij (jelmer) on 2012-03-22
Changed in bzr-pqm:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers