On Thu, Feb 06, 2020 at 10:17:54AM -0600, Segher Boessenkool wrote:
> > We would need to agree how do we express stuff going into different former
> > ChangeLog files, whether we require gcc/cp/ etc. prefixes before the lines,
> > or say require empty line for different former ChangeLog files and let the
> > extraction script figure it out from the changed files in the commit, etc.
>
> The latter seems error-prone, but maybe I worry too much :-)
Depends on how good the scripts are. The commit hook could figure out
cases which are non-ambiguous and the extraction script would handle those
and which cases are ambiguous and reject those.
>
> > We could have a rule that say New test. entries for newly added files
> > in */testsuite/* would be optional and let the generating script add those
> > (but say require entries if existing tests have been changed).
>
> How much work does that safe?
Some people don't like ChangeLog entries for testsuite additions (not me)
and in the official guidelines those are optional ATM I think.
Allowing them to be implicitly added for new testsuite files would hopefully
satisfy those, while allowing people who want to be more explicit (New
test. not being what they want to see for some reason e.g.) do so.
Jakub
