all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: no-spam@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Emacs release numbering 21.4 vs. 22.1
Date: 25 Feb 2004 16:43:38 +0100	[thread overview]
Message-ID: <m3y8qrupud.fsf_-_@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1Avz1S-0001M9-Na@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

>     The ^@^H[ stuff, which we invented for images, will also give us an
>     extensible mechanism, once Emacs Info ignores (and does not display) any
>     directives it doesn't know what to do with.  (I'll attach a test file.)
>     So in that sense, it is not *too* ugly a solution.
> 
> I think we want this change to be released in Emacs soon, if we are
> going to put it into Texinfo now.  We should put it into a 21.4
> release that we are going to make soon from the RC branch.

I believe many emacs users are expecting 21.4 be released from the CVS
head as a major feature update.  

To remove that confusion, I suggest that we decide _NOW_ that when CVS
head will eventually be released as 22.1, and that we start preparing
for that now.

We definitely have enough new functionality in the CVS head to justify
upgrading the major number (and I suppose that the unicode branch will
be merged to the trunk before releasing 22.1 -- right?).

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

  reply	other threads:[~2004-02-25 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 17:07 reliably determining if an Info node is an index Karl Berry
2004-02-21 14:55 ` Richard Stallman
2004-02-23 18:05   ` Karl Berry
2004-02-25 13:24     ` Richard Stallman
2004-02-25 15:43       ` Kim F. Storm [this message]
2004-02-25 16:23         ` Emacs release numbering 21.4 vs. 22.1 David Kastrup
2004-02-25 17:39           ` Stefan Monnier
2004-02-25 18:07             ` David Kastrup

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=m3y8qrupud.fsf_-_@kfs-l.imdomain.dk \
    --to=no-spam@cua.dk \
    --cc=emacs-devel@gnu.org \
    /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.