meaning of "Automatic date update in version.in" commits

[H.J. Lu]

On September 22, 2017 2:49:31 PM GMT+08:00, Andreas Schwab <schwab@linux-m68k.org> wrote:
>On Sep 22 2017, Petr Ovtchenkov <ptr@void-ptr.info> wrote:
>
>> I.e. development process of kernel or glibc (ABI is important and
>"source
>> identification" important too, isn't it?) dispense of such technique,
>
>Unlike kernel and glibc, libbfd and libopcodes do not maintain ABI
>compatibility, and never will.
>
>> but binutils prefer to follow tradition from 1994 that was useful
>> for publicly inaccessible CVS repo + public tarball on FTP.
>
>bfd/version.h has been added in 2001, not 1994.  It still works very
>well, no need to change anything that isn't broken.
>
>Andreas.
>
>-- 
>Andreas Schwab, schwab@linux-m68k.org
>GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276
>4ED5
>"And now for something completely different."

We should try not to update DATE in version.h if there is no change
otherwise.  It can be done by remembering the last commit.

Sent from my Android device with K-9 Mail. Please excuse my brevity.