From: Santi Béjar <sbejar@gmail.com>
Date: Mon, 16 Jun 2008 12:15:14 GMT
Subject: Re: current repository hash
Message-ID: <8aa486160806160515p751b2af4j2b0db6db7a9ad482@mail.gmail.com>
In-Reply-To: <556d90580806160451g36daefb6o48b93b92589211bf@mail.gmail.com>

On Mon, Jun 16, 2008 at 13:51, Alf Clement <alf.clement@gmail.com> wrote:
> Hi all,
>
> I want to compile the current repository hash id into my program, to
> be able to checkout later this
> id an see the exact files for the compile. It should flag if there are
> currently modified files in the
> directory tree.

You can look at how git does it:

http://git.kernel.org/?p=git/git.git;a=blob;f=GIT-VERSION-GEN;hb=HEAD

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

"git rev-parse HEAD" for a unique identifier,
but "git describe" is more convenient/useful.

> Do I need the 40 digit hash id?

Normally 7 or 8 are sufficient.

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

You can't. Even the 40 digit hash is "only" cryptographically unique.
But within a project 7 or 8 digits are unique enough for practical
use.

Santi