Hi, "pelzflorian (Florian Pelz)" <pelzflor...@pelzflorian.de> writes:
> 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? Our manual says in (info "(guix) Submitting Patches"): --8<---------------cut here---------------start------------->8--- Please write commit logs in the ChangeLog format (*note (standards)Change Logs::); you can check the commit history for examples. --8<---------------cut here---------------end--------------->8--- It's a "please", so not the strongest recommendation, but historically it's been asked to contributors to stick to it. So if we make a decision to change that we'd have to reword that paragraph. > Regarding double spaces, it should be documented if committers do not > have to insist. This doesn't even appear to be documented in our manual; it appears to have been encouraged/taught through reviews. The only place I can see it mentioned is in (info "(emacs) Sentences"): The sentence commands assume that you follow the American typist’s convention of putting two spaces at the end of a sentence. -- Thanks, Maxim
