When running on tty the commands pipe their output through less
automatically, so you don't need to mentally add "| less" anywhere.
-Let's get started. First off, we need a gitified SBCL repository
-to clone. At the time of writing there are two Git mirrors for
-the CVS history:
+Let's get started. First off, we need a gitified SBCL repository to
+clone. At the time of writing there are two Git mirrors for the CVS
+history:
git://sbcl.boinkor.net/sbcl.git
clones the SBCL Git mirror into the directory sbcl-git (there's a
naming convention in play here, but ignore that for now.) The clone
-contains full history, and is an independent repository on it's own
+contains full history, and is an independent repository on its own
right. Doing the clone takes as long as downloading 25Mb takes on your
line, but after that things are very fast.
git pull
-The directory .git inside the clone contains gits view of the
+The directory .git inside the clone contains Git's view of the
repository -- no other Git files or directories are in the tree. Just
for kicks:
nice in Git! The magic is: "git checkout -b hack-a-bit-more" -- but
leave that for another time.
-Let's do something. Edit version.lisp-expr, and maybe give SBCL some
-love.
+Let's do something. Edit BUGS, and maybe give SBCL some love.
git diff # shows you the changes in your tree
git status # shows you the state of files in the tree
Git has a notion of a separate "staging area", from which commits are
made. You can add content to the it by using git-add:
- git add version.lisp-expr
+ git add BUGS
git status
git diff
is silent!
By default git-diff shows the differences between the working tree and
-the staging area (or the last commit if the staging area is empty.)
+the staging area (which starts out identical to HEAD after a checkout).
-Edit version.lisp-expr again. Now you have three versions of it
-(ignoring all the historical versions for a second) to compare:
+Edit BUGS again. Now you have three versions of it (ignoring all the
+historical versions for a second) to compare:
git diff # between tree and staging area
- git diff HEAD # between tree last commit
+ git diff HEAD # between tree and last commit
git diff --cached # between staging area and last commit
If we were to do a git-commit now, it would commit the version in the
We like our latest version, so do
- git add version.lisp-expr
+ git add BUGS
again. Now the latest version is in the staging area, and version that
used to be there is gone. You don't need to worry about the staging
can be used to compare two arbitrary versions. The -w switch tells Git
to ignore whitespace changes -- you can usually leave it out, but it's
-nice when diffing across the great whilespacification patch.
+nice when diffing across the great whitespacification patches.
Onwards: just so that we have a bit more history on the branch, edit
-version.lisp-expr again, and git-commit again. You can use
+BUGS again, and git-commit again. You can use
git commit -a
would not have been automatic, but you would have been called to
resolve conflicts, etc.
-This is very nice for merging short-lived local branches, but not so
-good for merging things back onto master, or into "mainline" history:
+This is very nice for merging short-lived local branches, but not
+always so good for merging things back onto master, or into "mainline"
+history since you get all the commits that happened on the branch:
- * We don't want the version.lisp-expr from the branch, but a new one.
- (Once we live in the brave new distributed world we may want to
- rethink the version.lisp-expr a bit -- but that is neither here nor
- now.)
+ "first cut at x"
+ "first cut at y"
+ "oops, x was wrong"
+ "implemented z"
+ "aargh, x was still wrong"
+ ...
- * When merging a long-lived branch with several small commits it
- makes for a more readable history if we are able to merge it as a
- few logical patches.
+When merging a branch like this, with oopses in the history, it is far
+better if we are able to merge it as a few logical patches -- the
+resulting history will be easier to understand.
First option is to use --squash to squash all the commits into a
single one.
git checkout -b merge-experiment-2 master
git merge --squash hack-a-bit
-This has the side-effect of not committing the changes immediately, so
-we can edit version.lisp-expr to taste, and commit changes (remeber to
-git-add the edited version.lisp-expr.)
+This has the side-effect of not committing the changes immediately.
This is in effect similar to the usual way of merging back changes
from a CVS branch: if we're told that the patch came from a branch, we
to merge the changes upto a certain commit. Repeat a few times, and
you have the whole branch merged. Other Git commands provide more
-advanced options. See eg. git-cherry-pick.
+advanced options. See eg. git-cherry-pick, which you will end up
+using sooner or later.
Now, let's assume we have a private Git repository in ~/sbcl-git, and
we want to publish it to the world. The easiest way is to fire up a
box. Then you will be directed to set up an account, which you will
then have to add as a "pusher" to your SBCL fork.
-Finally, add the following snipped (adjusting for your own name) in
+Finally, add the following snippet (adjusting for your own name) in
~/sbcl-git/.git/config
[remote "public"]
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:
Finally, delete the foo-hacks-to-cvs branch after you've committed
code to CVS. Of course, instead of using git-cvexportcommit you can
also manually make and apply patches, etc. For hairier cases it may
-even be easier in the end.
+even be easier in the end:
+
+ git format-patch -p master..foo-hacks
+
+Generates a patch for each commit between master and the HEAD of
+foo-hacks, naming them
+
+ 0001-first-line-of-commit-message.patch
+ 0002-and-so-and-so-forth.patch
+ ...
+
+Due to, among other things, the cvs->git synchronization lag it is
+easy to get conflicts on version.lisp-expr so you may want to delay
+finalizing version.lisp-expr and the .msg file that cvsexportcommit
+produced by bumping the version and adding it to the commit message.
To get latest changes from the CVS Git mirror you originally cloned
from, do
proficient in using Git, but at least you should be up and walking.
Reading
- http://www.kernel.org/pub/software/scm/git/docs/everyday.html
-
-and
-
http://eagain.net/articles/git-for-computer-scientists/
+ http://www.kernel.org/pub/software/scm/git/docs/everyday.html
+ http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
-and various Git manual pages is a good idea, as is building a decent
-mental model of the way Git actually works. One command I can in
-particular recommend getting familiar with is git-rebase. git-gui,
-git-citool, and gitk provide graphical interfaces for working with
-Git.
+and various Git manual pages is a good idea.
+
+One command I can in particular recommend getting familiar with is
+git-rebase. git-gui, git-citool, and gitk provide graphical interfaces
+for working with Git -- particularly gitk is an invaluable tool for
+visualizing history.
projects / sbcl.git / blobdiff