John Ericson <l...@johnericson.me> writes: > I used to do that, but see commit > f0f728324021f38b0d31de399b9974535300167c : Dmitry opted to switch to > just using Git's commit messages as the source of truth, and providing > a make rule to generate the ChangeLog. > > The document you linked endorses such a choice, saying > >> Projects that maintain such VCS repositories can decide not to >> maintain separate change log files, and instead rely on the VCS to >> keep the change log. >> If you decide not to maintain separate change log files, you should >> still consider providing them in the release tarballs [...]. > > I think doing this is a fine decision.
The text you quoted means that you are meant to record the individual ChangeLog entries within each VCS log message, rather than updating a separate ChangeLog file with each check-in. These are subsequently reproduced in the generated ChangeLog file. It does not excuse you from writing log entries! Refer to Emacs commit messages: https://git.savannah.gnu.org/cgit/emacs.git/log?h=master for canonical examples of such log messages.
