Re: Git Questions

From: Jeff King <peff@peff.net>
Date: Aug 20, 2007, 10:06 UTC
Message-ID: <20070820100600.GA26843@coredump.intra.peff.net>
In-Reply-To: <1187603749.11595.10.camel@tom-desktop>

On Mon, Aug 20, 2007 at 07:25:48PM +0930, Tom Schinckel wrote:

> Is it possible to change the revision numbers from long hashes to normal
> numbers (i.e, 0001 for first, 0002 for the second)

No, they are a fundamental part of the way git works. However, there are a few ways you can avoid using the hashes:

 - tag your commits with readable names
 - use git's syntax for relative commits (e.g., "git-show HEAD~20") will
   show you 20 commits back from the current commit (where back is
   defined by following the first parent of each commit)

> a) Automatically commit a file to the repository every time it's saved

If you want git to notice when files are changed and commit them, then no. You can probably configure your editor (or whatever is saving the file) to trigger a 'git-add && git-commit'. But keep in mind this will produce a lot of commits with lousy commit messages.

> b) Automatically use the default hashed-out bit:

There isn't an argument to git-commit to do this, but you can get the same message from git-status. So you could do something like:

git-status | sed 's/^# //' | git-commit -F -

-Peff