all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: master cbef1e9 2/3: ; make change-history-commit
Date: Wed, 15 Apr 2015 14:30:34 -0700	[thread overview]
Message-ID: <552ED87A.3000405@cs.ucla.edu> (raw)
In-Reply-To: <21806.41548.239019.246211@gnu.org>

On 04/15/2015 10:39 AM, Glenn Morris wrote:
> maybe it is actually easier for people to correct the generated C'log,
> rather than figure out what commit log they should have written.
>

Yes, I think it's more natural.

I've done it the other way, with Coreutils, and the problem is that 
hacking on a ChangeLog edit script is one more thing for developers to 
learn, and that's a barrier to fixing ChangeLog history.  It's OK for 
Coreutils, whose few developers have been coached to write 
consistent-format commit messages and where people don't much care about 
a ChangeLog typo unless it's something important (like proper 
attribution).  It wouldn't work as well for for Emacs, which has dozens 
of developers not all of who are on the same page with regards to commit 
message format, and which has a greater emphasis on typo-free ChangeLog 
history.

Anyway, I installed the two changes we discussed, so we should be better 
off than we were before.



  reply	other threads:[~2015-04-15 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150409172246.20602.44549@vcs.savannah.gnu.org>
     [not found] ` <E1YgGAB-0005NP-Uc@vcs.savannah.gnu.org>
2015-04-09 18:24   ` master cbef1e9 2/3: ; make change-history-commit Glenn Morris
2015-04-09 20:26     ` Paul Eggert
2015-04-13  2:19       ` Glenn Morris
2015-04-13  6:58         ` Paul Eggert
2015-04-15 17:32           ` Glenn Morris
2015-04-15 17:39             ` Glenn Morris
2015-04-15 21:30               ` Paul Eggert [this message]
2015-04-09 22:35     ` Robin Templeton
2015-04-10  5:41       ` Paul Eggert
2015-04-11  4:33         ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=552ED87A.3000405@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.