Liam Hupfer <l...@hpfr.net> writes:

> <https://www.gnu.org/prep/standards/html_node/Change-Log-Concepts.html>
> acknowledges the points I’m discussing:
>
>> If a project uses a modern VCS to keep the change log information, as
>> described in Change Logs, explicitly listing the files and functions
>> that were changed is not strictly necessary, and in some cases (like
>> identical mechanical changes in many places) even tedious. It is up to
>> you to decide whether to allow your project’s developers to omit the
>> list of changed files and functions from the log entries, and whether
>> to allow such omissions under some specific conditions.
>
> Hey, it’s up to us! They do go on to mention some benefits. […]

Do we need a GCD even if we have permission to be more lax already?

Regarding double spaces, it should be documented if committers do not
have to insist.

If Liam wants to go as far as not listing files with non-automated
changes, I guess then yes, it would need a GCD.

Regards,
Florian

Reply via email to