From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: help system question
Date: Tue, 02 Jan 2007 12:17:58 -0700 [thread overview]
Message-ID: <eneb6p$m7i$1@sea.gmane.org> (raw)
In-Reply-To: <1167656440.834393.143110@a3g2000cwd.googlegroups.com>
Robert Thorpe wrote:
> Eli Zaretskii wrote:
>>> From: "Robert Thorpe" <rthorpe@realworldtech.com>
>>> Date: 31 Dec 2006 13:00:58 -0800
>>>
>>> Lots of people seem to have versions of Emacs 22 themselves, and don't
>>> seem to know that it hasn't been officially released. So people might
>>> think there is little difference between the Emacs22 they have and the
>>> finished one called 22.1. So, it might be a good idea to give the new
>>> version a higher version number.
>> I don't see a problem here (or misunderstand you): the current Emacs
>> 22 versions are numbered 22.0.NN, so when 22.1 is released, they will
>> know it's newer.
>
> Yes, but the implication is that it's only 0.5 of a version number
> newer. That doesn't indicate that the official v22.1 should be
> significantly more bug tested than 22.0.NN ones were.
That's exactly what it indicates: the 22.0.NN versions are pretest
versions (the most recent NN is 92), and 22.1 will be available
when the release criteria are met.
--
Kevin
next prev parent reply other threads:[~2007-01-02 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 9:25 help system question hbe123
2006-12-27 12:23 ` Eli Zaretskii
2006-12-27 13:08 ` Peter Dyballa
[not found] ` <mailman.2399.1167222233.2155.help-gnu-emacs@gnu.org>
2006-12-27 13:55 ` H.
2006-12-27 19:23 ` Eli Zaretskii
[not found] ` <mailman.2417.1167247424.2155.help-gnu-emacs@gnu.org>
2006-12-31 21:00 ` Robert Thorpe
2006-12-31 21:57 ` Eli Zaretskii
[not found] ` <mailman.2596.1167602241.2155.help-gnu-emacs@gnu.org>
2007-01-01 13:00 ` Robert Thorpe
2007-01-02 19:17 ` Kevin Rodgers [this message]
2007-01-02 21:35 ` Eli Zaretskii
[not found] ` <mailman.2669.1167773733.2155.help-gnu-emacs@gnu.org>
2007-01-03 11:25 ` Robert Thorpe
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='eneb6p$m7i$1@sea.gmane.org' \
--to=ihs_4664@yahoo.com \
/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.