bzr push preserve parent location?

[Alexander Belchenko]

John Arbash Meinel пишет:
> 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?
>>
> 
> 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?

I mean that after initial push new branch on remote location have the 
same parent as original branch.

More clear in my case: I have the branch on win32 machine. This branch 
have parent pointed to location on the same win32 machine 
(file:///I:/repo/branch/). I push (first time) this branch to remote 
linux machine via sftp transport. New branch on linux have the same 
parent location (file:///I:/repo/branch/) that absolutely have no sense 
on remote linux machine.

> 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.

This was subject of my question. I also think this is a bug. Minor bug. 
But I was unsure. Thanks for clarification.

--
Alexander