unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: lib/ should have its own ChangeLog
Date: Thu, 10 Feb 2011 10:43:12 -0800	[thread overview]
Message-ID: <4D5431C0.6070301@cs.ucla.edu> (raw)
In-Reply-To: <jwvfwrvvk3u.fsf-monnier+emacs@gnu.org>

On 02/10/2011 10:09 AM, Stefan Monnier wrote:
> Actually, the ChangeLog should contain the exact same text as the commit
> message, so we can eventually auto-generate the ChangeLog(s).

That sounds like a good idea, and I'm used to it in
other projects, such as coreutils.  How about if
we do that with Emacs too?  It is confusing and
wastes our time to keep two sets of logs when
one would do.



  reply	other threads:[~2011-02-10 18:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 22:39 lib/ should have its own ChangeLog Glenn Morris
2011-02-09 23:55 ` Paul Eggert
2011-02-10  6:36   ` [Bug-vc-dwim] " Ralf Wildenhues
2011-02-10  7:50     ` Paul Eggert
2011-02-10  2:43 ` Stefan Monnier
2011-02-10  4:00   ` Paul Eggert
2011-02-10  5:41     ` Eli Zaretskii
2011-02-10  4:52   ` Glenn Morris
2011-02-10  6:24     ` Paul Eggert
2011-02-10  7:04       ` Eli Zaretskii
2011-02-10  7:36         ` Paul Eggert
2011-02-10 10:30           ` Eli Zaretskii
2011-02-10 18:09           ` Stefan Monnier
2011-02-10 18:43             ` Paul Eggert [this message]
2011-02-10 19:58               ` Stefan Monnier
2011-02-12 23:44                 ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=4D5431C0.6070301@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).