unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: bug-vc-dwim@gnu.org, emacs-devel@gnu.org
Subject: Re: lib/ should have its own ChangeLog
Date: Wed, 09 Feb 2011 15:55:41 -0800	[thread overview]
Message-ID: <4D53297D.6060106@cs.ucla.edu> (raw)
In-Reply-To: <cu39nwde84.fsf@fencepost.gnu.org>

On 02/09/11 14:39, Glenn Morris wrote:
> I suggest the lib/ (and m4?) directory should have a separate ChangeLog,
> unless that makes syncing difficult for some reason.

I don't think it makes syncing hard, from gnulib to
Emacs.  I can do that.

However, it will make writing ChangeLog entries a bit harder,
since I use vc-dwim
<http://www.gnu.org/software/vc-dwim/> and it doesn't
support checking in a single change with entries in
multiple ChangeLogs.  I can simply not use vc-dwim for
such changes, I suppose.  (Or modify vc-dwim to support
that as a new feature. :-)

I'll CC: this to bug-vc-dwim to give them a heads-up.



  reply	other threads:[~2011-02-09 23:55 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 [this message]
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
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=4D53297D.6060106@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bug-vc-dwim@gnu.org \
    --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 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).