pqm-submit public location problems
james at jamesh.id.au
Fri Oct 20 04:17:42 BST 2006
On 18/10/06, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> pqm-submit seems a bit too aggressive in seeking out public locations.
> In particular, it falls back to using the parent location. But since
> the branch may be diverged from the parent location, this is frequently
> a bad choice.
> pqm-submit will also try to use the push location as a public location,
> but this is a bad idea because most push locations require authentication.
> So I'd like to change it to use
> 1. user option
> 2. public_repository configuration
> 3. the supplied location, if the protocol is not file://
I know some of the other defaults in older versions of pqm-submit
caused problems for Launchpad developers (pqm target branch mainly),
which we fixed by getting it to print an error message rather than
pick a default value.
This sounds like a similar case, so will reduce user confusion.
(Unless John can think of a good reason to keep the push location and
parent fallbacks in place).
More information about the bazaar