pull should always --remember

[John Arbash Meinel]

Martin Pool wrote:
> On 18/01/2006, at 9:09 AM, John Arbash Meinel wrote:
> 
>> Originally, we made 'bzr pull' keep the previous parent unless
>> '--remember' is supplied.
>> Now that we are changing bzr pull so that it defaults to a form of
>> --overwrite, I would like to see the default switch back to
>> '--remember'. Either that, or --overwrite automatically supplies --
>> remember.
>>
>> Basically, the reason we got rid of it, was because you might pull a
>> branch just to get their changes. But since we are changing  convergence,
>> I think only merge will really be used in that situation.
> 
> 
> That makes sense to me.  So it will be essentially a "this is a  mirror
> of X" setting.

Right, 'bzr pull' becomes 'mirror that other branch'. With a default
safety that it won't mirror if the branches are diverged. (which can be
fixed with --overwrite).
And then record what branch you mirrored.

> 
> Last I looked there was no obvious way to find out where it will pull 
> from or whether a default location.  It'd be nice to show that in say 
> "pull --show" and bzr info.
> 

I was thinking about a 'bzr parent', or something like that. The same
location is used for bzr missing, bzr merge, and other such commands.
But yes, we do need something for clients to request knowing what the
default remote location is.

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060117/1081f55e/attachment.pgp