From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Delanoe Eric <e.delanoe@gea.fr>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Could GIT manage revision headers embedded in code ?
Date: Tue, 2 May 2017 17:54:28 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705021751250.3480@virtualbox> (raw)
In-Reply-To: <135C7A92C7D64E488B830ADC2970C70132AE6407@SVGEA-EMAIL.gea.fr>
Hi Eric,
On Tue, 2 May 2017, Delanoe Eric wrote:
> Could this kind of "keyword expansion" feature be added into GIT ?
Back in the days, it was decided that this should be part of the "export
as zip" functionality, see the `export-subst` feature in git-archive's and
gitattributes' documentation.
In reality, what most projects do is to generate a header or some such as
part of their build process. Git itself may serve as a case in point:
https://github.com/git/git/blob/master/GIT-VERSION-GEN
used in
https://github.com/git/git/blob/v2.12.2/Makefile#L390-L392
Ciao,
Johannes
prev parent reply other threads:[~2017-05-02 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 11:48 Could GIT manage revision headers embedded in code ? Delanoe Eric
2017-05-02 12:11 ` Christian Couder
2017-05-02 13:33 ` Delanoe Eric
2017-05-02 15:54 ` Johannes Schindelin [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=alpine.DEB.2.20.1705021751250.3480@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=e.delanoe@gea.fr \
--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 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).