If you look at the tarball that is downloaded you'll see that we give you
the short hash.  If you want the .git folder you should just clone the repo,
because that's created by your local git when you clone.  You could also
just hit the tag page and parse the commit off that,
http://github.com/Dieterbe/uzbl/tree/2009.11.30.  There might also be a way
to get that info from the API.

    Tekkub
    GitHub Tech Support
    http://support.github.com/
    Join us on IRC: #github on freenode.net
    Discussion group: [email protected]

On Sat, Dec 12, 2009 at 11:14 AM, Dieter_be <[email protected]>wrote:

> Hi,
> when we release software we tag it, push the tag and give the tarball
> url to downstream.
> ie: http://github.com/Dieterbe/uzbl/tarball/2009.11.30
>
> but the problem is, in the make process we need to know which commit
> hash you're compiling from, so we can store that in the binaries. it
> helps in identifying the software.
> (see http://github.com/Dieterbe/uzbl/blob/master/Makefile )
>
> for this we currently use the .git directory, but this directory is
> not available in the tarballs.
>
> is it possible for github to do one of:
> - leaving .git intact in the tarball
> - put a little file in the tarball, containing the commit hash and
> optionally the tag
>
> or alternatively, is their some trick we can do ourselves to have a
> file which always contains the current commit hash? i think svn can do
> something like that, but couldn't find it for git.
>
> thanks!
> Dieter
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "GitHub" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<github%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/github?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/github?hl=en.


Reply via email to