Re: ChangeLog and commit messages

[Dmitry Gutov]

On 19/06/2023 19:59, Eli Zaretskii wrote:
> > Date: Mon, 19 Jun 2023 14:57:23 +0300
> > Cc: Eli Zaretskii<eliz@gnu.org>,emacs-devel@gnu.org
> > From: Dmitry Gutov<dmitry@gutov.dev>
> >
> > On 19/06/2023 13:10, Po Lu wrote:
> > > At my organization, which uses SVN, each new revision
> > > is required to change only one file, and updates to ChangeLog are
> > > performed separately after all edits are checked in and the
> > > corresponding files are unlocked.  This is also the same policy that was
> > > used by Emacs development in the CVS days, I think.
> > Sounds like your organization uses a fairly antiquated workflow.
> >
> > Luckily, we're a few steps ahead now in Emacs development.
> Was this really an opinion worthy of making public?  How is it
> supposed to be helpful for a serious discussion to derogate the
> participants?

I wasn't talking about the participants (who might well all be competent 
programmers), just about the workflow.

But the phrasing was not great, I suppose. Apologies.

> The man was asked to describe his use case, so he did
> it.  It makes no sense to reprimand him for telling us what we asked
> to hear.

That's not all, though. He expressed a general opinion about what should 
go into commit messages, and what should go into ChangeLog:

> Which is the problem with the ``shortlog'' concept: detailed
descriptions of these changes should be placed in ChangeLog, and the VCS
should concentrate on tracking revisions to each file.