This is the mail archive of the
mailing list for the binutils project.
Re: Can the automatic daily update commits be stopped, take 2
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: David Howells <dhowells at redhat dot com>
- Cc: Binutils <binutils at sourceware dot org>, Nick Clifton <nickc at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>, Andreas Schwab <schwab at linux-m68k dot org>, Will Newton <will dot newton at linaro dot org>
- Date: Thu, 28 Jan 2016 15:01:18 -0800
- Subject: Re: Can the automatic daily update commits be stopped, take 2
- Authentication-results: sourceware.org; auth=none
- References: <20428 dot 1420542531 at warthog dot procyon dot org dot uk> <25281 dot 1454021771 at warthog dot procyon dot org dot uk>
On Thu, Jan 28, 2016 at 2:56 PM, David Howells <email@example.com> wrote:
> David Howells <firstname.lastname@example.org> wrote:
>> Can the automatic "daily update" and "Automatic date update in version.in"
>> commits be stopped? Or at least only performed if the last commit was not
>> itself such a commit?
> I note that these are still being produced. Is it possible to stop them as
> they make a mess of the git history?
> I think Andreas Schwab suggested that it might be necessary as you can't
> directly compare two git hashes without a repo handy to give them context -
> but how often is that actually a problem? If you are comparing two points on
> the same branch, you can consult the ChangeLog files and if they're produced
> separate branches, then comparing the dates is potentially meaningless anyway.
> Further, not having an incrementing version doesn't necessarily mean that you
> can't name published tarballs for the date on which they're produced.
I don't mind stopping updating bfd/version.h as long as "ld --version"
displays different versions from linkers of different dates.