This is the mail archive of the
mailing list for the binutils project.
Re: meaning of "Automatic date update in version.in" commits
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Matt Rice <ratmice at gmail dot com>
- Cc: Fiodar Stryzhniou <fedor_qd at mail dot ru>, Andreas Schwab <schwab at linux-m68k dot org>, Petr Ovtchenkov <ptr at void-ptr dot info>, Binutils <binutils at sourceware dot org>, Joel Brobecker <brobecker at adacore dot com>, Matthias Klose <doko at ubuntu dot com>, GDB <gdb at sourceware dot org>
- Date: Thu, 21 Sep 2017 17:17:07 +0000
- Subject: Re: meaning of "Automatic date update in version.in" commits
- Authentication-results: sourceware.org; auth=none
- References: <yyRSFRMK2lz0.xJ9T1cbZ@smtp.mail.ru> <CACTLOFoyTeU+CG9vo8Xf+tWmr7869c_NMrRNUo4X90Ov9S2DyQ@mail.gmail.com>
On Thu, 21 Sep 2017, Matt Rice wrote:
> option A. seems to be using git smudge/filter to on checkout populate
> the version.in using a smudge rule, and then filtering it out using a
> acting much like the RCS keywords...
> pros: no extra commit stuff at all
> cons: requires setting up git config stuff in the repository for
> executing the smudge/filter rules on checkout
> this should likely be checked by the configure process e.g.
> configure should produce an error telling the user to enable the
> smudge/filter rules
> when the version is $Date$ rather an actual date...
I don't think there should be anything that requires people to check out
in a special way, or to configure their checkouts specially, rather than
just using "git clone" and a subsequent build. Generic tools such as
build bots may have generic knowledge of how to check out and update git
checkouts; they should not need binutils-specific extras to that
Joseph S. Myers