X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=inline;f=doc%2FGIT-FOR-SBCL-HACKERS.txt;fp=doc%2FGIT-FOR-SBCL-HACKERS.txt;h=e4dcd7bd300020da5a48c61ffa617b4e8322ba10;hb=624598d2a9f14336cac4bf74b85b972a1085580f;hp=ae9446bc83f1e56d0b0238cf68d4bea25a31ea32;hpb=69b12095da6db9ac97e347dbc155091de79472cc;p=sbcl.git

diff --git a/doc/GIT-FOR-SBCL-HACKERS.txt b/doc/GIT-FOR-SBCL-HACKERS.txt
index ae9446b..e4dcd7b 100644
--- a/doc/GIT-FOR-SBCL-HACKERS.txt
+++ b/doc/GIT-FOR-SBCL-HACKERS.txt
@@ -282,7 +282,7 @@ issues manually:
  .msg                    -- holds the commit message
 
 Finally, delete the foo-hacks-to-cvs branch after you've committed
-code to CVS. Of course, instead of using git-cvexportcommit you can
+code to CVS. Of course, instead of using git-cvsexportcommit you can
 also manually make and apply patches, etc. For hairier cases it may
 even be easier in the end:
 
@@ -307,6 +307,10 @@ from, do
 
 on the branch you want to update on your private repository.
 
+Note that if you edit version.lisp-expr in the CVS tree and not before
+then the cvs commit command that git-cvsexportcommit prints does not
+list version.lisp-expr, so don't copy paste it.
+
 This completes our whirlwind tour. I'm not saying this makes you
 proficient in using Git, but at least you should be up and walking.
 Reading