On 07/05/2018 04:07 AM, Richard Biener wrote:
On Thu, Jul 5, 2018 at 9:47 AM Aldy Hernandez <al...@redhat.com> wrote:
After 20 years of hacking on GCC I feel like I have literally wasted
days of my life typing out ChangeLog entries that could have easily been
generated programmatically.
Can someone refresh my memory here, what are the remaining arguments for
requiring ChangeLog entries?
I vaguely recall Jakub (or Alex Oliva??) mentioning that they were
desired for releases. If this is the case, may I volunteer to write the
necessary scripts to generate these automatically?
It would be nice if we could have meaningful commit messages explaining
why we are doing things, and any list of changed files be generated on
the fly.
Sorry, I'm getting old, and would hate to spend any meaningful remaining
time typing things that a computer can do for me.
They are definitely useful in my day-to-day work when tracking down changes
given I can easily grep them. >
I think that any change here should be _after_ we've switched to git (finally).
I've been hearing about the death of svn for well over a decade. Do we
have an ETA for the official git switch?
However, even if you could "git log --grep" the commit messages, I
assume your current use is grepping for function names and such, right?
Being able to grep a commit message won't solve that problem, or am I
missing something?
I still think we could automate all this: auto-generated per release?
Kept up to date with latest "make changelog"? As a git/svn hook? With
some sort of GCC static analysis plugin to really drill and document
what was actually changed?
Is there something y'all foresee that can't be addressed automatically?
Aldy
