From: "Avery Pennarun" <apenwarr@gmail.com>
To: stuart.freeman@et.gatech.edu
Cc: git@vger.kernel.org
Subject: Re: Best practice question
Date: Thu, 19 Jun 2008 12:39:19 -0400 [thread overview]
Message-ID: <32541b130806190939t2a26c6f7j987eb1c679d53b3a@mail.gmail.com> (raw)
In-Reply-To: <485A6E03.6090509@et.gatech.edu>
On 6/19/08, D. Stuart Freeman <stuart.freeman@et.gatech.edu> wrote:
> My project has an "about" page that lists the version. I understand why
> git doesn't do keyword expansion, but I'm wondering if there's a
> recommended best practice for keeping that up to date.
If you compile git yourself and run "git --version", it contains the
current version number. You may want to do it the same way.
See also the "git-describe" command.
Have fun,
Avery
prev parent reply other threads:[~2008-06-19 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 14:32 Best practice question D. Stuart Freeman
2008-06-19 14:54 ` Karl Hasselström
2008-06-19 15:40 ` Santi Béjar
2008-06-19 16:39 ` Avery Pennarun [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=32541b130806190939t2a26c6f7j987eb1c679d53b3a@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=stuart.freeman@et.gatech.edu \
/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).