From: Nick Roberts <nickrob@snap.net.nz>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest 22.0.99
Date: Tue, 24 Apr 2007 17:48:56 +1200 [thread overview]
Message-ID: <17965.39496.572942.836736@farnswood.snap.net.nz> (raw)
In-Reply-To: <87ejma1o37.fsf@stupidchicken.com>
> If no problems are found in this over the next few days, I think we
> should release Emacs 22.1; but I guess that's up to RMS to decide.
This sounds sensible to me. How about numbering bug fix releases, which
presumably could be made shortly after the main release if necessary, 22.1.1,
22.1.2, ... this time? In the past there has been some confusion about the
content of 21.2, 21.3 and 21.4, which AFAICS were bascically just respins of
21.1.
If signifacnt changes are released before Unicode Emacs, these could be
numbered 22.2, 22.3 etc.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-04-24 5:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 2:51 Emacs pretest 22.0.99 Chong Yidong
2007-04-24 5:48 ` Nick Roberts [this message]
2007-04-24 6:13 ` Eli Zaretskii
2007-04-24 6:26 ` Nick Roberts
2007-04-24 12:10 ` Eli Zaretskii
2007-04-24 22:53 ` Nick Roberts
2007-04-25 3:26 ` Eli Zaretskii
2007-04-25 3:57 ` Nick Roberts
2007-04-25 18:02 ` Eli Zaretskii
2007-04-24 21:35 ` Richard Stallman
2007-04-24 22:57 ` Nick Roberts
2007-04-25 14:52 ` Richard Stallman
2007-04-24 6:27 ` Lennart Borgman (gmail)
2007-04-24 7:40 ` Lennart Borgman (gmail)
2007-04-24 7:59 ` Jason Rumney
2007-04-24 8:16 ` Lennart Borgman (gmail)
2007-04-24 8:29 ` Jason Rumney
2007-04-24 8:35 ` Lennart Borgman (gmail)
2007-04-24 8:44 ` Jason Rumney
2007-04-24 11:05 ` Lennart Borgman (gmail)
2007-04-24 8:03 ` Takashi Hiromatsu
2007-04-24 12:24 ` Eli Zaretskii
2007-04-25 0:41 ` Takashi Hiromatsu
2007-04-27 13:21 ` Eli Zaretskii
2007-05-01 7:08 ` Takashi Hiromatsu
2007-05-04 13:38 ` Eli Zaretskii
2007-04-26 23:17 ` Giorgos Keramidas
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=17965.39496.572942.836736@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=cyd@stupidchicken.com \
--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 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).