Re: vc-update for bzr etc.

[Stefan Monnier <monnier@iro.umontreal.ca>]

>>> So the full functionality for Bzr should be something like this:
>>> - If it's a bound branch, do bzr update.
>>> - Otherwise, if there is a default pull location, prompt for a location
>>> and do "bzr merge --pull".
>>> - Otherwise, just do "bzr merge --pull" to use the default location.
>>> Does this sound right?
>> 
>> If it's not bound, it should just use "bzr pull" without prompting
>> the user, IMO.

> The "bzr pull" operation only works if the branches have not diverged.
> If the vc pull operation corresponds to "bzr pull", then what would it
> do in git?  IIUC, git pulls perform merging automatically, so if vc-pull
> does "bzr pull" in bzr and "git pull" in git, it would be doing two
> different things.

> That's why I thought the closest common denominator would be to use
> bzr's "merge --pull".

VC tries to present a uniform UI and that is good, but trying to impose
a uniform semantics to all commands is asking too much.  So I think it's
perfectly OK for vc-pull/update to do "bzr pull" for Bzr and
"git pull" for Git, even if they don't do exactly the same thing.


        Stefan