2.37 branch and ChangeLogs

[Hans-Peter Nilsson]

On Thu, 17 Jun 2021, Nick Clifton via Binutils wrote:
>   Once the 2.37 branch has been created, we are going to relax the
>   requirement that patch submissions include text for changelog
>   entry(s).  Instead we are going to use the details from the git commit
>   messages.  This does mean that these messages must include accurate
>   details concerning the author(s) and contents of the patches.
>
>   Changelog entries can still be submitted with a patch, should the
>   author so wish, but the commit messages must also be complete.
>
>   I will be investigating how to collect together git commit messages
>   and turn them into changelog like files for when a release is
>   generated, so that releases will still retain full details of the
>   patches that they contain.

I endorse re-using the GCC solution, with complete, formatted
changelog entries as part of the git commit log and automated
extraction to the respective ChangeLog (piggy-backed on the
snapshot scripts).  Or, at least something compatible with the
corresponding workflow, so maintainers don't have to remember
that the rules are different.

I hope the practical problems are manageable with different
rules in gdb and binutils and whatnot with the different
directories.

brgds, H-P