[EMAIL PROTECTED] (Karl Berry) wrote: ... > but we'd commit changes only against the git repo > > That was my point. Have you written a cheat sheet for coreutils git > users? Or maybe one exists independently? You know, > (a) how to check out
On the command line, it's probably best to start off using cogito wrappers. That hides git's "index" concept, which can be a little annoying, at first. Run this to create a checked-out directory named "any-name-you-want": cg-clone git://git.sv.gnu.org/coreutils any-name-you-want or omit the destination dir-name to create a directory named "coreutils": cg-clone git://git.sv.gnu.org/coreutils > (b) how to update cg-pull > (c) how to commit [into your local copy of the repository] cg-commit Browsing a local repository, it can be nice to use one of the GUI-based tools, like qgit or gitk. But there's much more. There are many use cases outlined in git's own Documentation directory. E.g., http://www.kernel.org/pub/software/scm/git/docs/tutorial.html http://www.kernel.org/pub/software/scm/git/docs/everyday.html
