pqm-submit: support for bound branches

[Aaron Bentley]

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

Robert Collins wrote:
> === modified file 'a/pqm_submit.py'
> --- a/pqm_submit.py
> +++ b/pqm_submit.py
> @@ -93,6 +93,12 @@
>      target_base = config.public_branch()
>  
>      if not target_base:
> +        try:
> +            target_base = branch.get_bound_location()
> +        except AttributeError:
> +            pass
> +
> +    if not target_base:
>          target_base = branch.get_push_location()
>  
>      if not target_base:
> 
> 
> 
> This lets one have a branch bound to its nominal public location, which
> is sftp published to a slightly different url, and submit from the
> public location by:
> 
> bzr push
> bzr pqm-submit -m foo

Here's my topology:

  panometrics.com
  ^         ^
  /          \
 V            V
Home         Work

I am constantly pulling from the public location, and pushing to a
private one.  It's essentially, a manual bound branch.  So I would
prefer that the order went:

1. parent location
2. bound location
3. push location

I have to say, I think it will be unusual for a branch to be bound to
its public location, because the binding implies writing, implies SFTP,
implies non-public.

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

iD8DBQFEDGJ90F+nu1YWqI0RApckAJ46jvGW5kBFQ5MC1aAK/uUGEY/sTACghwyJ
v5fAI5EY+0kUZHUoLJnNbqs=
=k3Jf
-----END PGP SIGNATURE-----