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 22:27:22 +0100 [thread overview]
Message-ID: <201001162227.23236.jnareb@gmail.com> (raw)
In-Reply-To: <a1138db31001161312i2c032c38tcc0fb162c61fbb35@mail.gmail.com>
Dnia sobota 16. stycznia 2010 22:12, Paul Richards napisał:
> 2010/1/16 Jakub Narebski <jnareb@gmail.com>:
>> Paul Richards <paul.richards@gmail.com> writes:
>>> 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.
>> 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.
>
> Thanks, it appears though that "git describe" does not work in Cygwin git. :(
If you got something like
$ git describe
fatal: cannot describe 'a27cb622b30f18cb8510b7b3856d4029e617d95b'
it means that you don't have any tags in your history. You should tag your
releases (released versions) using annotated tags.
Anyway you have
$ git describe --always
a27cb62
--
Jakub Narebski
Poland
prev parent reply other threads:[~2010-01-16 21:27 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
2010-01-16 21:12 ` Paul Richards
2010-01-16 21:26 ` Shawn O. Pearce
2010-01-16 21:27 ` Jakub Narebski [this message]
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=201001162227.23236.jnareb@gmail.com \
--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 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).