From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: ChangeLogs in the elpa branch
Date: Mon, 26 Sep 2011 12:26:53 -0400 [thread overview]
Message-ID: <pdsjnjjmlu.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvsjnj8nn9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 26 Sep 2011 09:03:54 -0400")
Stefan Monnier wrote:
> The decision for Emacs ChangeLogs was "to keep them for now".
I'm very much against getting rid of ChangeLogs, but every time the
issue has been mentioned it has been with some kind of "but we won't do
this now", so I never know when to voice my objections. Seems like now
may be too late, and this is not a democracy anyway, but here goes:
Reasons I object to getting rid of ChangeLogs:
1) Using Emacs VC, you only have to write the ChangeLog, then use C-c
C-a to insert it into the commit buffer. So there is no need to "write
the same thing twice".
2) Sometimes I want to put more detail into the commit log, which is
not appropriate for the ChangeLog.
3) ChangeLogs can be edited to correct mistakes, commit logs cannot.
4) I have the impression that having to write ChangeLogs leads to
higher quality entries than just using commit logs would.
Reasons I can see why people want to do this:
1) It makes merging between branches a bit easier.
I don't think this is a compelling reason to change practice.
bzr has a changelog_merge plugin that makes this easier, and I wrote
some notes on how to use it with Emacs. Anyone who feels burdended by
having to merge ChangeLogs between branches should try it out. It seems
like a simple problem, conceptually.
Personally I think the slight extra time involved in maintaining a
ChangeLog is more than justified by the higher quality of said log.
next prev parent reply other threads:[~2011-09-26 16:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:09 ChangeLogs in the elpa branch Michael Albinus
2011-09-26 9:56 ` Julien Danjou
2011-09-26 10:23 ` Lars Magne Ingebrigtsen
2011-09-26 10:35 ` Michael Albinus
2011-09-26 14:23 ` Ted Zlatanov
2011-09-26 15:52 ` Stefan Monnier
2011-09-26 16:49 ` Ted Zlatanov
2011-09-26 21:13 ` Richard Stallman
2011-09-26 11:46 ` Dave Abrahams
2011-09-26 13:03 ` Stefan Monnier
2011-09-26 13:49 ` Michael Albinus
2011-09-26 16:26 ` Glenn Morris [this message]
2011-09-26 16:38 ` Lars Magne Ingebrigtsen
2011-09-26 19:18 ` Andreas Schwab
2011-09-26 17:06 ` Eli Zaretskii
2011-09-26 17:08 ` Stefan Monnier
2011-09-26 21:18 ` Michael Albinus
2011-09-26 21:27 ` Lars Magne Ingebrigtsen
2011-09-27 3:10 ` Michael Albinus
2011-09-27 5:22 ` Bastien
2011-09-27 8:57 ` Andreas Schwab
2011-09-27 9:04 ` Bastien
2011-09-27 9:25 ` Eli Zaretskii
2011-09-27 13:00 ` Stefan Monnier
2011-09-27 7:10 ` Glenn Morris
2011-09-27 9:05 ` Juanma Barranquero
2011-09-27 9:45 ` joakim
2011-09-27 12:02 ` Stephen J. Turnbull
2011-09-27 13:05 ` Stefan Monnier
2011-09-27 9:00 ` Juanma Barranquero
2011-09-27 12:24 ` Thien-Thi Nguyen
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=pdsjnjjmlu.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
/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.