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.
John
On 9/14/23 01:37, Po Lu wrote:
John Ericson <l...@johnericson.me> writes:
I had meant to just deal with windows-gnu in those 3 options,
otherwise we have a combinatorial explosion of patches (and commit
messages) for me to write :). Once we deal with that one we can deal
with the others, right?
Incidentally, if you want to make it easier for others to interpret your
patches, please provide ChangeLog entries along with them. Refer to
`(standards)Change Logs':
https://www.gnu.org/prep/standards/standards.html#Change-Logs
