On Thu, Apr 30, 2020 at 03:29:10PM +0200, Martin Liška wrote:
> $ ./changelog.py
> patches/1957-c-generic-lambda-forwarding-function-PR94546.patch
> OK
> ------ gcc/cp/ChangeLog ------
> 2020-04-22 Jason Merrill <ja...@redhat.com>
>
> PR c++/94546
> * pt.c (register_parameter_specializations): If the instantiation is
> still a parameter pack, don't wrap it in a NONTYPE_ARGUMENT_PACK.
> (tsubst_pack_expansion, tsubst_expr): Adjust.
> ------ gcc/testsuite/ChangeLog ------
> 2020-04-22 Jason Merrill <ja...@redhat.com>
>
> gcc/testsuite/g++.dg/cpp2a/lambda-generic-variadic20.C: New file.
If this is what is really created, then for the new file, missing * space,
gcc/testsuite/ that shouldn't be there and missing PR c++/94546 line above
it.
> Currently supported features can be seen here: [4]. Feel free to test the
> script
> and suggest what can we improve. Our integration plan is to come up with
> a new git hook that will first work only in a reporting mode (no commits
> refusal).
> Later on, we can add the automatic generation of ChangeLog entries.
Once it is enforced we'd probably disallow touching ChangeLog files in a
commit with other changed files and during the
maintainer-scripts/update_version_git
script ought to check in in addition to the DATESTAMP updates in the same
commit also updates to all the ChangeLog files since the last DATESTAMP
commit. That way, if there is some ChangeLog entry screw-up that gets
through the script, one could still wait until DATESTAMP update and
afterwards in a separate commit adjust the ChangeLog files.
Jakub
