Can the automatic daily update commits be stopped, take 2

[Mike Frysinger]

On 28 Jan 2016 15:01, H.J. Lu wrote:
> On Thu, Jan 28, 2016 at 2:56 PM, David Howells <dhowells@redhat.com> wrote:
> > David Howells <dhowells@redhat.com> 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.

s/dates/source trees (e.g. diff git sha1)/
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://sourceware.org/pipermail/binutils/attachments/20160128/953716b6/attachment.sig>