From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: Should we move 20.x related stuff out of NEWS ?
Date: 16 Apr 2004 10:31:28 +0900 [thread overview]
Message-ID: <buoekqo909b.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <871xmp136a.fsf@mail.jurta.org>
Juri Linkov <juri@jurta.org> writes:
> I must say that having news for old releases in one file is very
> inconvenient.
I agree, I've often been annoyed by this. It's a bit hard to say what's
better though -- it really depends on the version the user is upgrading
from, and we can't know that!
-Miles
--
I'm beginning to think that life is just one long Yoko Ono album; no rhyme
or reason, just a lot of incoherent shrieks and then it's over. --Ian Wolff
next prev parent reply other threads:[~2004-04-16 1:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 17:40 Should we move 20.x related stuff out of NEWS ? Kim F. Storm
2004-04-15 18:55 ` Juri Linkov
2004-04-16 1:31 ` Miles Bader [this message]
2004-04-16 2:08 ` David Kastrup
2004-04-16 2:33 ` Miles Bader
2004-04-16 13:28 ` Stefan Monnier
2004-04-17 14:09 ` Juri Linkov
2004-04-18 21:47 ` Richard Stallman
2004-04-17 7:15 ` Richard Stallman
2004-04-17 8:42 ` Alan Mackenzie
2004-04-17 14:09 ` Juri Linkov
2004-04-18 14:35 ` Alan Mackenzie
2004-04-18 17:10 ` Adrian Aichner
2004-04-18 17:21 ` Adrian Aichner
2004-04-18 21:39 ` Kim F. Storm
2004-04-19 6:58 ` Kai Grossjohann
2004-04-19 10:26 ` Alan Mackenzie
2004-04-22 3:18 ` Juri Linkov
2004-04-22 23:38 ` Kim F. Storm
2004-04-25 4:55 ` Juri Linkov
2004-04-25 23:36 ` Richard Stallman
2004-04-26 4:59 ` Juri Linkov
2004-04-26 6:18 ` Miles Bader
2004-04-26 14:10 ` Richard Stallman
2004-04-22 2:54 ` isearch (was: Re: Should we move 20.x related stuff out of NEWS ?) Juri Linkov
2004-04-23 17:21 ` Richard Stallman
2004-04-23 17:44 ` Stefan Monnier
2004-04-23 18:35 ` Drew Adams
2004-04-16 18:08 ` Should we move 20.x related stuff out of NEWS ? 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=buoekqo909b.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=storm@cua.dk \
/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).