bzr push preserve parent location?

[John Arbash Meinel]

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

Alexander Belchenko wrote:
> Today I discover that bzr push is preserve parent location. Even if it
> have no sense for pushed copy. Is this intended behavior?
> 
> -- 
> Alexander

I'm not sure what you mean by preserving the parent location. Does the
remote location already have a parent which it isn't changing? Is it
setting the parent of the remote object to self? Is it setting the
parent of the remote object to the parent of self?

As near as I can tell, we seem to set the parent of the remote object to
the parent of self.

This only happens with the initial push, future pushes do not update the
remote parent. (It happens because an initial push is actually closer to
a 'clone' operation).

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.

So, probably we should file a bug on this. IMO a branch created from
push should not have a parent.

John
=:->

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

iD8DBQFFNbOmJdeBCYSNAAMRAkRcAKCESd8WKyZ5ZuAeKHIJtxhE4ieORgCfY2JG
HZqx88JqYPgkZyP26n6Olb0=
=Am3s
-----END PGP SIGNATURE-----