From: "Robert Thorpe" <rthorpe@realworldtech.com>
Subject: Re: help system question
Date: 3 Jan 2007 03:25:53 -0800 [thread overview]
Message-ID: <1167823553.553042.15250@s34g2000cwa.googlegroups.com> (raw)
In-Reply-To: <mailman.2669.1167773733.2155.help-gnu-emacs@gnu.org>
Eli Zaretskii wrote:
> > From: "Robert Thorpe" <rthorpe@realworldtech.com>
> > That doesn't indicate that the official v22.1 should be
> > significantly more bug tested than 22.0.NN ones were.
>
> Who said it's significantly more bug-free? As someone who
> participates in Emacs pretests since v19.30, I cannot in good faith
> say that the official version is so much more stable than the pretest
> one.
I see. In that case v22.1 is a reasonable version number to use.
I mentioned this because often projects write great extra features but
their users only find out years/months later when they upgrade to
another new version. This is because the authors have only incremented
the version number by a small amount the first time, so users don't
notice. That doesn't sound like what's happening here though.
prev parent reply other threads:[~2007-01-03 11:25 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
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 [this message]
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=1167823553.553042.15250@s34g2000cwa.googlegroups.com \
--to=rthorpe@realworldtech.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.
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).