From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: 21.2.90 pretest, 21.3, 21.4...
Date: Wed, 6 Nov 2002 16:18:36 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1021106161559.6963A-100000@is> (raw)
In-Reply-To: <shel9zmbf9.fsf@tux.gnu.franken.de>
On Wed, 6 Nov 2002, Karl Eichwalder wrote:
> My idea is to prepare those patches mainly for internal release
> management purposes (but it wouldn't hurd to make them available on
> alpha, too). Prepare pre-releases as usual, do testing. Now, when a
> serious problem with the already released version pops up, fix just
> this problem and release a fixed version immediately.
You assume that in the meantime no changes were done in the CVS, which is
normally not the case.
Also, an entirely new tarball for each bug sounds excessive (each one is
20MB compressed, remember?).
> PITA, that the gnu announce group is empty
> since ages -- as long as you (not you personally) don't fix the
> announce channels you don't have a right to complain about the lack of
> manpower.
I didn't complain. Someone needs to step forward to fix gnu.announce as
well.
next prev parent reply other threads:[~2002-11-06 14:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 16:16 21.2.90 pretest, 21.3, 21.4 Juanma Barranquero
2002-11-04 18:31 ` Stefan Monnier
2002-11-05 6:05 ` Eli Zaretskii
2002-11-05 7:02 ` Karl Eichwalder
2002-11-05 8:02 ` Juanma Barranquero
2002-11-05 18:40 ` Eli Zaretskii
2002-11-05 20:44 ` Karl Eichwalder
2002-11-06 6:29 ` Eli Zaretskii
2002-11-06 6:58 ` Karl Eichwalder
2002-11-06 14:18 ` Eli Zaretskii [this message]
2002-11-08 10:32 ` Kai Großjohann
2002-11-07 15:07 ` Richard Stallman
2002-11-05 8:02 ` Juanma Barranquero
2002-11-05 18:56 ` Eli Zaretskii
2002-11-05 12:02 ` Kai Großjohann
2002-11-05 19:00 ` Eli Zaretskii
2002-11-05 20:50 ` Stefan Monnier
2002-11-06 6:33 ` Eli Zaretskii
2002-11-06 12:40 ` Kim F. Storm
2002-11-06 12:55 ` Juanma Barranquero
2002-11-06 14:25 ` Eli Zaretskii
2002-11-06 14:49 ` Juanma Barranquero
2002-11-06 14:51 ` Miles Bader
2002-11-07 22:02 ` Francesco Potorti`
2002-11-07 8:08 ` (no subject) Kenichi Handa
2002-11-08 12:06 ` Richard Stallman
2002-11-07 22:00 ` 21.2.90 pretest, 21.3, 21.4 Francesco Potorti`
2002-11-09 11:54 ` Richard Stallman
2002-11-06 7:28 ` Kai Großjohann
2002-11-06 14:19 ` Eli Zaretskii
2002-11-06 7:49 ` Juanma Barranquero
2002-11-05 18:39 ` Stefan Monnier
2002-11-05 19:17 ` Eli Zaretskii
2002-11-05 20:37 ` Stefan Monnier
2002-11-06 6:00 ` Eli Zaretskii
2002-11-05 5:58 ` Eli Zaretskii
2002-11-05 7:56 ` Juanma Barranquero
2002-11-05 18:54 ` Eli Zaretskii
2002-11-05 20:40 ` Juanma Barranquero
2002-11-06 6:13 ` Eli Zaretskii
2002-11-06 4:49 ` Richard Stallman
2002-11-06 8:25 ` Juanma Barranquero
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 15:58 jasonr
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=Pine.SUN.3.91.1021106161559.6963A-100000@is \
--to=eliz@is.elta.co.il \
--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).