Re: VC state

[Dan Nicolaescu <dann@ics.uci.edu>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

  > I tried to use vc-status with Bzr and found that VC still needs some
  > work to adjust it to current VCS realities:

Please add to vc.el:Todo the items that are not already there.

  > - `vc-update' should do a `bzr pull'.
  > - `vc-merge' only operates on a single file.
  > - `vc-merge' takes revisions as arguments rather than a branch (plus
  >   optional revisions).
  > 
  > The above changes will require changing some of the backend operations,
  > since those operations will need to somehow return a list of files
  > changed.
  > 
  > The vc-status UI also needs more work:

The main question for vc-status is: should it be bound to C-x v d now?
It's already better than vc-dired. And it would be good if more people
use it/hack on it to shake the remaining bugs sooner rather than later.

  > - there should be a way to operate on (sub)directories.

You mean something more than M-x vc-status DIR/SUBDIR RET ?

  > - it should be possible to add an entry in the display (like PCL-CVS's
  >   `I') so as to then operate on it.

Interesting, didn't know about this feature.  I'll implement this.

  > - indicate files with conflicts (probably requires changes in backends
  >   as well to provide that info).

This has been in Todo for a while, displaying this stuff is trivial, VC
needs just to provide the information.  Someone just needs to sit down
and figure out how it's supposed to work in VC...

  > - the modeline says "*VC status* from *vc-status*".

Fixed.