changeset 94811:47dff47e1b61

Comment and to-do list fixes.

--- a/lisp/vc-dispatcher.el	Fri May 09 18:47:36 2008 +0000
+++ b/lisp/vc-dispatcher.el	Fri May 09 18:59:45 2008 +0000
@@ -58,13 +58,8 @@
 ;; of the file tree from the state of the currently visited buffer 
 ;; and returns that subset, presumably to a client mode.
 ;;
-;; The user may be attempting to select one of three contexts: an
-;; explicitly selected fileset, the current working directory, or a
-;; global (null) context.  The user may be looking at either of two
-;; different views; a buffer visiting a file, or a directory buffer
-;; generated by vc-dispatcher.  The main UI problem connected with
-;; this mode is that the user may need to be able to select any of
-;; these three contexts from either view.
+;; The user may be looking at either of two different views; a buffer
+;; visiting a file, or a directory buffer generated by vc-dispatcher.
 ;;
 ;; The lower layer of this mode runs commands in subprocesses, either
 ;; synchronously or asynchronously.  Commands may be launched in one
@@ -119,8 +114,6 @@
 ;;
 ;; - vc-dir needs mouse bindings.
 ;;
-;; - vc-dir needs more key bindings for VC actions.
-;;
 ;; - vc-dir toolbar needs more icons.
 ;;
 ;; - vc-dir-next-line should not print an "end of buffer" message when
@@ -296,7 +289,7 @@
 
 ;;;###autoload
 (defun vc-do-command (buffer okstatus command file-or-list &rest flags)
-  "Execute a VC command, notifying user and checking for errors.
+  "Execute a slave command, notifying user and checking for errors.
 Output from COMMAND goes to BUFFER, or *vc* if BUFFER is nil or the
 current buffer if BUFFER is t.  If the destination buffer is not
 already current, set it up properly and erase it.  The command is

--- a/lisp/vc.el	Fri May 09 18:47:36 2008 +0000
+++ b/lisp/vc.el	Fri May 09 18:59:45 2008 +0000
@@ -552,6 +552,8 @@
 
 ;;; Todo:
 
+;; - vc-dir needs more key bindings for VC actions.
+;;
 ;; - vc-update/vc-merge should deal with VC systems that don't
 ;;   update/merge on a file basis, but on a whole repository basis.
 ;;
@@ -592,9 +594,6 @@
 ;;   `diff-add-change-log-entries-other-window' to create a detailed
 ;;   skeleton for the log...
 ;;
-;; - a way to do repository wide log (instead of just per
-;;   file/fileset) is needed.  Doing it per directory might be enough...
-;;
 ;; - most vc-dir backends need more work.  They might need to
 ;;   provide custom headers, use the `extra' field and deal with all
 ;;   possible VC states.