Unbind should make the branch the stored location for push/pull

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

Servilio Afre Puentes wrote:
> Public bug reported:
>
> If there is no previous stored location, this is the most logical
> behaviour and should be done by default, and would enable an easy
> workflow like:
>
> $ bzr co URL
> [... work ...]
> $ bzr unbind # going to airport
> [... more work ..]
> $ bzr push # arrived at sprint
> [... more sprinting, more planes ...]
> $ bzr bind # and back home
>
> When there is a push/pull location stored, then only override if an
> option is present.
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>

Seems reasonable.

 status: confirmed
 importance: medium
 tags: easy

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksBhUMACgkQJdeBCYSNAAMyqgCgq/ZHB9LlqkUtI6fcEYA1ul6T
fHgAoMUbX4/F933XXMRTRb0+bQwI2IO+
=b0df
-----END PGP SIGNATURE-----

Hmm, I would prefer that bzr defaults to the bound_location iff no push/pull location is set *and* the branch is not bound.

You can't use 'bzr pull :bound' when unbound... but with bzr >= 2.3 you can use 'bzr push `bzr config bound_location`' ;)

I forgot to add that *setting* push_location and/or parent_location when unbinding will make it harder to push somewhere else when needed (you may use a bound branch for developing a feature or fixing a bug and *then* push the result somewhere else for review).

Closely related to #98644