Re: vc-update for bzr etc.

[Chong Yidong]

Stefan Monnier <address@hidden> writes:

> Better to just use the new backend function if present and fallback (or
> provide a default implementation that delegates) to the old
> backend function.

OK, sounds reasonable.

>> +   "Update the current Bzr repository."
>
> I have no idea what "Update the current Bzr repository" means.
>
>> +       (vc-bzr-command "update" t 'async nil))))
>
> This will not do what it says in non-bound branches.

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?