all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: old ChangeLog files
Date: 13 Dec 2002 12:45:14 +0100	[thread overview]
Message-ID: <5x65ty16t1.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <7704-Fri13Dec2002111852+0200-eliz@is.elta.co.il>

"Eli Zaretskii" <eliz@is.elta.co.il> writes:

> > From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
> > Date: Thu, 12 Dec 2002 09:30:49 -0500
> > 
> > Ideally this should also be merged into `ChangeLog' itself, but
> > CVS performs poorly with large locally-modified files, so
> > it's more convenient to keep a "small" ChangeLog file and move
> > older stuff into ChangeLog.old.
> > 
> > What do people think ?
> 
> It sounds like a good idea, but won't that cause ChangeLog.old to
> grow indefinitely (assuming that Emacs is going to be maintained for
> many years to come ;-)?
> 
> If the file becomes too large, it might become difficult to browse it
> with e.g. Less or even Emacs itself.

IMO, it would be simpler to provide key bindings in Changelog mode
that automatically takes you to the previous older / next newer
changelog file in a series of ChangeLog files.

Maybe we could even have PgUp/PgDn doing this automatically at the
top/bottom of the current changelog file.

A similar thing could be done for NEWS files...


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2002-12-13 11:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 14:30 old ChangeLog files Stefan Monnier
2002-12-12 14:46 ` Miles Bader
2002-12-13  8:18 ` Eli Zaretskii
2002-12-13 11:45   ` Kim F. Storm [this message]
2002-12-13 10:25     ` Eli Zaretskii
2002-12-13 12:30       ` Kim F. Storm
2002-12-13 12:12     ` Kenichi Handa
2002-12-14 18:32   ` 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

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

  git send-email \
    --in-reply-to=5x65ty16t1.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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.