More consistency for Git log messages?

[Jonathan Wakely]

On Mon, 28 Dec 2020, 23:55 Gerald Pfeifer, <gerald@pfeifer.com> wrote:

> Having spent a bit more time with GCC sources (as opposed to wwwdocs)
> recently and looking for prior art to guide me, I noticed there's a
> lot of options to specific the ChangeLog file(s) to use.
>
> And correspondingly a lot of inconsistency.
>
> Right now we seem to allow for
>
>  1. gcc/cp/ChangeLog
>  2. gcc/cp/ChangeLog:
>  3. gcc/cp
>  4. gcc/cp:
>  5. gcc/cp/
>
> and probably more.
>

We also allow not specifying the directory at all, if it can be deduced
from the changed files.



> Can we streamline this a bit and converge on one of the forms 3-5?
>
> Personally I'd suggest 3 (the shortest) or 5 (the directory), but whatever
> ... as long as things become more consistent, which is easier on newbies
> and reading logs (or automatically processing them later on).
>

We already process them automatically.

It's worth noting that some people generate then automatically too, and the
mklog.py hook uses form 2 IIRC.