X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2FGIT-FOR-SBCL-HACKERS.txt;fp=doc%2FGIT-FOR-SBCL-HACKERS.txt;h=ca442e73b447872086d4799ce3877604104ba139;hb=62c1c94106fca74b3d191c9576cc635aaf5592bb;hp=264766facd15b61460315dda4c206eee33b5acce;hpb=0d9184c70988bfa5d99e4a25368c155c9ced63ed;p=sbcl.git

diff --git a/doc/GIT-FOR-SBCL-HACKERS.txt b/doc/GIT-FOR-SBCL-HACKERS.txt
index 264766f..ca442e7 100644
--- a/doc/GIT-FOR-SBCL-HACKERS.txt
+++ b/doc/GIT-FOR-SBCL-HACKERS.txt
@@ -264,6 +264,17 @@ wish to commit the changes you have wrought on branch foo-hacks
  review, fix any problems
  cvs commit -F .msg
 
+To make things a bit easier, add eg. this stanza to ~/sbcl-git/.git/config:
+
+ [alias]
+    sbcl-export = ! cd ~/sbcl-cvs && GIT_DIR=~/sbcl-git/.git git-cvsexportcommit -v
+
+Then you can just run
+
+ git sbcl-export foo-hacks-to-cvs
+
+from inside ~/sbcl-git/, and have it prepare your CVS tree for commit.
+
 git-cvsexportcommit is fairly conservative by default, and will fail
 if the patch doens't apply cleanly. If that happens, you can fix the
 issues manually: