summaryrefslogtreecommitdiff
path: root/lisp/vc/vc-git.el
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2014-12-01 20:00:40 -0500
committerEric S. Raymond <esr@thyrsus.com>2014-12-01 20:00:40 -0500
commit7d2110560e17744d8a1969b1a3df6040f7e90440 (patch)
tree261d09669acab312568db3896e9486c698a04294 /lisp/vc/vc-git.el
parentb7fd432d56e352e25e6db4eaf5b081ddc5a39367 (diff)
downloademacs-7d2110560e17744d8a1969b1a3df6040f7e90440.tar.gz
Update the git backend's header comment.
Diffstat (limited to 'lisp/vc/vc-git.el')
-rw-r--r--lisp/vc/vc-git.el6
1 files changed, 4 insertions, 2 deletions
diff --git a/lisp/vc/vc-git.el b/lisp/vc/vc-git.el
index 93a129c1fc4..93c5ff805f6 100644
--- a/lisp/vc/vc-git.el
+++ b/lisp/vc/vc-git.el
@@ -50,6 +50,8 @@
;; STATE-QUERYING FUNCTIONS
;; * registered (file) OK
;; * state (file) OK
+;; * dir-status (dir update-function) OK
+;; - dir-status-files (dir files ds uf) NOT NEEDED
;; * working-revision (file) OK
;; - latest-on-branch-p (file) NOT NEEDED
;; * checkout-model (files) OK
@@ -65,13 +67,13 @@
;; * checkout (file &optional rev) OK
;; * revert (file &optional contents-done) OK
;; - rollback (files) COULD BE SUPPORTED
-;; - merge (file rev1 rev2) It would be possible to merge
+;; - merge-file (file rev1 rev2) It would be possible to merge
;; changes into a single file, but
;; when committing they wouldn't
;; be identified as a merge
;; by git, so it's probably
;; not a good idea.
-;; - merge-news (file) see `merge'
+;; - merge-news (file) see `merge-file'
;; - steal-lock (file &optional revision) NOT NEEDED
;; HISTORY FUNCTIONS
;; * print-log (files buffer &optional shortlog start-revision limit) OK