unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: src/ChangeLog
Date: Sun, 23 Sep 2007 18:00:03 -0700	[thread overview]
Message-ID: <200709240100.l8O103xN017990@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <18164.26686.457566.622403@kahikatea.snap.net.nz> (Nick Roberts's message of "Sat\, 22 Sep 2007 12\:56\:30 +1200")

Nick Roberts <nickrob@snap.net.nz> writes:

  > I see src/ChangeLog has been split into src/ChangeLog and src/ChangeLog.10
  > at the date at which version 22.1 was released (2007-06-02).  I think it
  > should be split here:
  > 
  > 2007-04-24  Chong Yidong  <cyd@stupidchicken.com>
  > 
  > 	* Branch for 22.1.
  > 
  > I think I added this entry even though it has Chong's name (as he made
  > the branch).  I think this is the important date from the point of view of
  > the ChangeLog because changes after it are generally *not* in Emacs 22.1.
  > In particular my gpm changes, currently recorded in src/ChangeLog.10, are
  > only in trunk.
  > 
  > If someone wants to know exactly which changes after 2007-04-24 are in 22.1
  > they have to look at src/ChangeLog on the EMACS_@@_BASE branch, of course.

This makes me think that it would be great if isearch in ChangeLog
would know to start searching the next ChangeLog.XX file when getting
to the end of the current one.  We have the infrastructure to do this
now, it just needs a bit of coding...

  parent reply	other threads:[~2007-09-24  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22  0:56 src/ChangeLog Nick Roberts
2007-09-22 15:48 ` src/ChangeLog Richard Stallman
2007-09-25  9:35   ` src/ChangeLog Nick Roberts
2007-09-24  1:00 ` Dan Nicolaescu [this message]
2007-09-24  1:22   ` src/ChangeLog Juri Linkov
2007-10-05  5:50     ` src/ChangeLog Dan Nicolaescu
2007-09-24 18:20   ` src/ChangeLog Richard Stallman

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=200709240100.l8O103xN017990@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    /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).