From: Jakub Narebski <jnareb@gmail.com>
To: Paul Richards <paul.richards@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Stamp Git commit id into file during build process
Date: Sat, 16 Jan 2010 11:35:34 -0800 (PST) [thread overview]
Message-ID: <m3d419desd.fsf@localhost.localdomain> (raw)
In-Reply-To: <a1138db31001161050i73eade1bif968ca1256dcef2c@mail.gmail.com>
Paul Richards <paul.richards@gmail.com> writes:
> Hi,
> I am in the process of migrating from Subversion to Git. One thing I
> am unsure of is how to stamp the 'version' or 'commit id' into a file
> as part of a build process.
>
> With subversion I used the SubWCRev tool from TortoiseSVN
> (http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-subwcrev.html).
>
> With Git I imagine that I'd like to put a copy of the current commit
> id (either the full hash or a truncated version of that) into a file
> which then gets included into the program source code in some way.
>
> Is there a recommended way of doing this with git? Perhaps with
> something similar to SubWCRev?
>
> Currently I am thinking about using "git log", and grepping the output
> in some way so that I just get the hash.
Not "git log".
Take a look how for example git project and Linux kernel use "git describe"
in GIT-VERSION-GEN script, and how they use GIT-VERSION-GEN script in the
Makefile.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-01-16 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 18:50 Stamp Git commit id into file during build process Paul Richards
2010-01-16 19:14 ` Erik Faye-Lund
2010-01-16 19:15 ` Erik Faye-Lund
2010-01-16 19:17 ` Sverre Rabbelier
2010-01-16 19:22 ` Erik Faye-Lund
2010-01-16 19:29 ` Sverre Rabbelier
2010-01-16 19:35 ` Jakub Narebski [this message]
2010-01-16 21:12 ` Paul Richards
2010-01-16 21:26 ` Shawn O. Pearce
2010-01-16 21:27 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3d419desd.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=paul.richards@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.