all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Subject: Cleaning up NEWS, ONEWS, ... files
Date: Tue, 30 May 2006 12:37:03 +0200	[thread overview]
Message-ID: <m3ac8zsss0.fsf@kfs-l.imdomain.dk> (raw)


There is currently NO logic in what goes into NEWS, ONEWS, ONEWS.1, etc.

I suggest (and will do the work if accepted) that we reorganize
the NEWS files so that 

NEWS is about the current release, i.e. 22.x

NEWS.21 is about emacs 21.x  (split from current NEWS)

NEWS.20 is about emacs 20.x  (split from current NEWS)

NEWS.19 is about emacs 19.x  (from ONEWS)

NEWS.18 is about emacs 18.x  (from ONEWS.4 and ONEWS.3)

NEWS.17-1 is about emacs 17 and older (from ONEWS.2 and ONEWS.1)

This allows us to write clear and consistent information in NEWS about
where to find information about older releases.

Of course, I'll update view-emacs-news to still DTRT when
given a prefix arg.  (C-u C-h C-n).

BTW, if already visiting a NEWS file, using C-h C-n could
automatically take you to an older or newer NEWS file, depending
on whether you are in the top or bottom half of the NEWS file.

Then, each NEWS file could say

At the top of the file:
      Use C-h C-n to view newer NEWS

At the bottom of the file:
      Use C-h C-n to view older NEWS

instead of explicitly mention which file to visit...

That would be a fairly trivial, and self-contained change!

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

             reply	other threads:[~2006-05-30 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 10:37 Kim F. Storm [this message]
2006-05-31  0:40 ` Cleaning up NEWS, ONEWS, ... files Richard Stallman
2006-05-31 13:57   ` Kim F. Storm
2006-06-01 19:35     ` Richard Stallman
2006-06-04  1:18   ` Kim F. Storm

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=m3ac8zsss0.fsf@kfs-l.imdomain.dk \
    --to=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 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.