Re: Why are so many great packages not trying to get included in GNU Emacs? WAS: Re: Making Emacs more friendly to newcomers

[Konstantin Kharlamov]

On Sat, 2020-06-13 at 20:38 +0100, João Távora wrote:
> On Sat, Jun 13, 2020, 15:36 Dmitry Gutov <dgutov@yandex.ru> wrote:
> > On 13.06.2020 14:59, Konstantin Kharlamov wrote:
> > > no other projects require
> > > writing down a list of functions I changed just for the fun of it
> > 
> > As a reviewer, there's something to be said about having an overview of 
> > the whole diff (which can get long) in a few paragraphs on top of the 
> > patch. A good commit message like that actually makes a lot of things 
> > clear in advance.
> 
> +1. I even use this for my own projects or projects where it's not required.
> Producing that list is a last self-reviewing step that summarizes _how_ the
> change was implemented. The diff itself is the ultimate source, but a summary
> is it very welcome.
> 
> Of course most good commit messages don't stop there, they also explain the
> _why_.
> 
> In general, Konstantin. I think your "for fun" exemplifies how you and many
> others think of these procedures as spurious, or gratuitous. But they're not,
> they exist because she people, whom you may disagree with, find them useful.

Oh, sure I can be mistaken. I see you replied to Dmitry's email, I had a follow-
up on it. Does my follow-up mail change your opinion, or perhaps do you have
some example in mind that a good commit message without the list would not
solve?