Re: current repository hash

From: David Tweed <david.tweed@gmail.com>
Date: Jun 16, 2008, 12:11 UTC
Message-ID: <e1dab3980806160511s1a9a5192gbdf6539205ef1865@mail.gmail.com>
In-Reply-To: <556d90580806160451g36daefb6o48b93b92589211bf@mail.gmail.com>

On Mon, Jun 16, 2008 at 12:51 PM, Alf Clement <alf.clement@gmail.com> wrote:

> What would be the best command to get a unique identifier?

Note that git itself does this via the GIT-VERSION-GEN script so you could look at that for ideas.

> How can I make sure that a shorter hash id will be unique?

Theoretically isn't that going to be tricky, as you don't just want something that's unique at the time you compile the program but which won't potentially be rendered non-unique by later commits (after you've released your binary)? If you just want to be reasonably sure you can truncate the hash to the length you'd like, eg "addcc13a" for 8 characters and run

git rev-parse addcc13a

and see if it says

addcc13a fatal: ambiguous argument 'addcc13a': unknown revision or path not in the working tree. Use '--' to separate paths from revisions

-- 
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"while having code so boring anyone can maintain it, use Python." --
attempted insult seen on slashdot