From: Erik Faye-Lund <kusmabite@googlemail.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 20:15:51 +0100 [thread overview]
Message-ID: <40aa078e1001161115r312f2e7ahbe9bab6c28b3ad2e@mail.gmail.com> (raw)
In-Reply-To: <40aa078e1001161114w5a65bebbhaf43317634899925@mail.gmail.com>
On Sat, Jan 16, 2010 at 8:14 PM, Erik Faye-Lund
<kusmabite@googlemail.com> wrote:
> the "git describe"-tool, which gives a nice and short description of
> the commit relative to the most recent commit.
>
...by "most recent commit", I mean "most recent tag". Sorry about that.
--
Erik "kusma" Faye-Lund
next prev parent reply other threads:[~2010-01-16 19:15 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 [this message]
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
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=40aa078e1001161115r312f2e7ahbe9bab6c28b3ad2e@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).