pqm-submit doesn't know how to push.

[Robert Collins]

This means that when I pqm-submit I do:
bzr push --overwrite && bzr pqm-submit <...>

Further to that, because pushing has a delay with lp for the public
branch to be updated, this will sometimes fail with 'branch <X> does not
have revision <Y>'

So, this would be a lot better as:
bzr pqm-submit --overwrite --push <...>

Where it would push; and if the public url != the push url spin for
(say) 61 seconds waiting for the revision to propogate, then submit.

 affects bzr-pqm
 status confirmed
 importance medium

[Vincent Ladeuil (vila)]

I often use a bound branch as the base for my submissions, so I'd prefer a way to tell pqm-submit: Hey ! I know the stuff is there, keep trying a bit please, won't be long: --try 5min ?

[Martin Pool (mbp)]

> bzr pqm-submit --overwrite --push <...>

This seems a bit like a maladaption for pqm's approach of merging from
a public branch, rather than taking a merge proposal directly...

--
Martin <http://launchpad.net/~mbp/>

[Robert Collins (lifeless)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
>> bzr pqm-submit --overwrite --push <...>
>
> This seems a bit like a maladaption for pqm's approach of merging from
> a public branch, rather than taking a merge proposal directly...

I certainly agree that PQM's interface can be improved; this simply
tries to make the current interface more tolerable.

- -Rob

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqwHmYACgkQ42zgmrPGrq5tLwCfSSxkDuvH8ASGFgHKbUA+HPkJ
voIAoJniXLKVA2dAwcvszIFp0JJ60Ezc
=MUmk
-----END PGP SIGNATURE-----