From: Per Starback <starback@ling.uu.se>
Cc: emacs-devel@gnu.org
Subject: Re: old emacs announcemente
Date: 09 Apr 2003 13:48:10 +0200 [thread overview]
Message-ID: <qzsmsrj3id.fsf@tempus.ling.uu.se> (raw)
In-Reply-To: <E192JES-000133-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> The question about 21.3's release as already been asked in the
> pretester's list,
>
> Why in the world ask the pretester's list?
> To get the answer, ask the people who know the answer.
It is pointless to test a pretest version after the release of the
real version, so pretester *should* always be informed of new
releases.
I thought that was obvious and it was only by mistake that pretesters
haven't been informed of the last couple (or more?) of releases, but
if you think it's natural that pretesters don't know if there have
been a release I guess this must be pointed out to avoid the same
situation happening again in the future.
next prev parent reply other threads:[~2003-04-09 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 23:24 old emacs announcemente Francesco Potorti`
2003-03-23 7:44 ` Adrian Mrva
2003-04-06 11:36 ` Juanma Barranquero
2003-04-06 12:09 ` Adrian Mrva
2003-04-06 13:03 ` Juanma Barranquero
2003-04-06 16:09 ` Jason Rumney
2003-04-06 20:28 ` Juanma Barranquero
2003-04-06 23:07 ` Richard Stallman
2003-04-07 16:27 ` Juanma Barranquero
2003-04-08 2:30 ` Richard Stallman
2003-04-09 11:48 ` Per Starback [this message]
2003-04-10 6:23 ` Richard Stallman
2003-04-10 17:42 ` Kevin Rodgers
-- strict thread matches above, loose matches on Subject: below --
2003-04-13 9:11 Lars Hansen
2003-04-14 2:36 ` Richard Stallman
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=qzsmsrj3id.fsf@tempus.ling.uu.se \
--to=starback@ling.uu.se \
--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).