This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v2] Script to generate ChangeLog-like output
On 14/01/19 8:08 PM, Siddhesh Poyarekar wrote:
Thanks, the plan is to actively maintain the script to add features all
the way into 2.30 and maybe even 2.31. The idea of stopping ChangeLog
writing in 2.29 is to allow us to clean up patchwork and start cleaning
up our own workflows so that we can automate our patch reviews (or at
least begin the process) by 2.30 release. That way by 2.31 we will have
the automation in place.
It is of course a pie-in-the-sky kind of plan but hopefully we will be
able to pull it off. As for the script, I have added it is a project in
our local makerspace (I get requests from students for projects,
hopefully this is a simple enough start) and if it is considered
important enough for GSoC, I don't mind mentoring students working
globally on additional backends for the script.
I've also thought about some other aspects of this:
1. Should this be a separate project that does only the job of
generating a ChangeLog from any git log?
2. Should this be rewritten in C/C++ to make it significantly faster?
Probably not a priority, but maybe something worth thinking about?
This of course is orthogonal to the glibc question, which this script
should be capable of solving since a significant chunk is C code.
Siddhesh