bzr push preserve parent location?

[Aaron Bentley]

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

Martin Pool wrote:
> Tangentially, I think we should probably get away from calling them
> 'parent' locations, because it can cause this kind of confusion.  It no
> longer seems like a good idea to assume there's commonly a single place
> you push to and pull from.  Instead 'remembered push location' or
> 'default push location'.

What I'd be interested in supporting is a single 'mirror_from', and
multiple 'merge_from' locations.  Someone in IRC also expressed the
desire for push to update multiple locations at a time.

>>I think it makes sense to not set the remote parent at all. It might
>>make sense to set it to self, but you don't know what route other would
>>have to self.
> 
> 
> Well, it would be consistent with 'bzr branch' if it set the remote
> parent to point back to the origin.

Since the origin is necessarily a file:// location, I think that's more
likely to cause problems than the current behavior, which may preserve a
publicly-accessible parent URL.

>  Really it would clean things up
> more if we fixed bzr branch to allow creation of a new remote branch.

Makes sense.

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

iD8DBQFFN6Co0F+nu1YWqI0RApuzAJ4wTqkikNoLl5buYm/XYJ5RCIXjygCeM9Qw
S7U/YLX4wz9vXGvYL6Sy6M8=
=qC7y
-----END PGP SIGNATURE-----