This is the mail archive of the
mailing list for the binutils project.
Can the automatic daily update commits be stopped, take 2
- From: David Howells <dhowells at redhat dot com>
- To: binutils at sourceware dot org
- Cc: dhowells at redhat dot com, nickc at redhat dot com, brobecker at adacore dot com, schwab at linux-m68k dot org, hjl dot tools at gmail dot com, will dot newton at linaro dot org
- Date: Thu, 28 Jan 2016 22:56:11 +0000
- Subject: 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>
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.