From: Dan Nicolaescu <dann@ics.uci.edu>
To: Juri Linkov <juri@jurta.org>
Cc: Nick Roberts <nickrob@snap.net.nz>, emacs-devel@gnu.org
Subject: Re: src/ChangeLog
Date: Thu, 04 Oct 2007 22:50:42 -0700 [thread overview]
Message-ID: <200710050550.l955okIb028614@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <87ps08g8n7.fsf@jurta.org> (Juri Linkov's message of "Mon\, 24 Sep 2007 04\:22\:04 +0300")
Juri Linkov <juri@jurta.org> writes:
> > > 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...
>
> This would be easy, but the question is in the evil details. Once details
> are agreed, the implementation is straightforward.
emacs uses:
ChangeLog ChangeLog.12 ChangeLog.11 ...
gcc uses:
ChangeLog ChangeLog-2006 ChangeLog-2005 ...
So it seems that ordering by the numeric suffix could work.
> IIRC, there was an idea to specify the set of files to isearch
> in the Local Variables section.
That's also good, but it requires knowledge to write the correct
incantation in the Local Variables section...
next prev parent reply other threads:[~2007-10-05 5:50 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 ` src/ChangeLog Dan Nicolaescu
2007-09-24 1:22 ` src/ChangeLog Juri Linkov
2007-10-05 5:50 ` Dan Nicolaescu [this message]
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=200710050550.l955okIb028614@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).