From: "D. Stuart Freeman" <stuart.freeman@et.gatech.edu>
To: git@vger.kernel.org
Subject: Best practice question
Date: Thu, 19 Jun 2008 10:32:35 -0400 [thread overview]
Message-ID: <485A6E03.6090509@et.gatech.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 248 bytes --]
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.
--
D. Stuart Freeman
Georgia Institute of Technology
[-- Attachment #2: stuart_freeman.vcf --]
[-- Type: text/x-vcard, Size: 162 bytes --]
begin:vcard
fn:D. Stuart Freeman
n:Freeman;Douglas
email;internet:stuart.freeman@et.gatech.edu
tel;work:(404)385-1473
x-mozilla-html:FALSE
version:2.1
end:vcard
next reply other threads:[~2008-06-19 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 14:32 D. Stuart Freeman [this message]
2008-06-19 14:54 ` Best practice question Karl Hasselström
2008-06-19 15:40 ` Santi Béjar
2008-06-19 16:39 ` Avery Pennarun
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=485A6E03.6090509@et.gatech.edu \
--to=stuart.freeman@et.gatech.edu \
--cc=git@vger.kernel.org \
/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.