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: Tue, 27 Sep 2011 03:10:42 -0400 [thread overview]
Message-ID: <m7h4uxxxp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: jwvty7zdynz.fsf-monnier+emacs@gnu.org
Stefan Monnier wrote:
>> 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".
>
> That doesn't seem like an objection but more like a reason why you're
> willing to live with the duplication.
OK. But much of the motivation to make the change seems to be "there will
be less to type". I'm saying I don't find that compelling.
I find the extra work involved in maintaining a ChangeLog to be worth it.
(Did I miss some other reason why this change is desirable, beyond
"somewhat fewer keypresses", and "slightly easier merging between
branches"?
CVS had both editable logs, and a cvs2log program, so what's changed?
I guess it's that people tend to use more branches now, and find merging
ChangeLogs difficult? As I said, try the changelog_merge plugin for
that. Or don't keep (versioned) ChangeLogs in your personal branches.)
>> 2) Sometimes I want to put more detail into the commit log, which is
>> not appropriate for the ChangeLog.
>
> Without stating why, I can't assess how serious this is.
It tends to be things like adding hrefs to emacs-devel discussions, or
explaining more _why_ a change is needed as opposed to simply stating
what the change was.
>> 3) ChangeLogs can be edited to correct mistakes, commit logs cannot.
>
> That's not written in stone. CVS can edit its commit logs, and there's
> no reason the same can't be done for other revision control systems.
Shall we wait till bzr gets a good implementation of this feature then?
> Better yet: there's no reason we can't do it ourselves in a (potentially
> even backend-agnostic) way that will work for C-x v l and for
> auto-generation of a ChangeLog file.
This doesn't sound "better" to me.
>> 4) I have the impression that having to write ChangeLogs leads to
>> higher quality entries than just using commit logs would.
>
> I think this just reflects the better support in change-log-mode, with
> highlighting, C-x 4 a and things like that.
I disagree, I think people take more care with ChangeLogs.
next prev parent reply other threads:[~2011-09-27 7:10 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
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 [this message]
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=m7h4uxxxp.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.