From: Karl Eichwalder <keichwa@gmx.net>
Cc: Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>, emacs-devel@gnu.org
Subject: Re: 21.2.90 pretest, 21.3, 21.4...
Date: Tue, 05 Nov 2002 08:02:42 +0100 [thread overview]
Message-ID: <shd6pksdm5.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <Pine.SUN.3.91.1021105075909.16406B-100000@is> (Eli Zaretskii's message of "Tue, 5 Nov 2002 08:05:29 +0200 (IST)")
Eli Zaretskii <eliz@is.elta.co.il> writes:
> For 21.3, maybe. But for 21.2, I disagree.
With 21.1 and 21.2 you can destroy your files easily (even RMS was
bitten once[1]); the ordinary user isn't able to those encoding related
problems on his own. Thus, please release 21.3 ASAP -- 21.3 is _very_
important for European users. I don't understand why it takes that
long to release a version fixing these encoding related problems.
I know, resources are limited, but this must not mean to ignore or delay
serious problems. I also put some time in testing the RC and said it is
better than the previous version; but I cannot test a bug fix release
again and again; I need some features from HEAD for my daily work.
Bug fix releases must happen in a timely manner -- otherwise they take
away to many resources from all of us.
________________
[1] Cf.:
From: Richard Stallman <rms@gnu.org>
Subject: Several serious problems
To: handa@etl.go.jp, spiegel@gnu.org, savannah-hackers@gnu.org
Cc: emacs-devel@gnu.org
Reply-To: rms@gnu.org
Date: Mon, 22 Jul 2002 11:11:35 -0600 (MDT)
Message-Id: <200207221711.g6MHBZo02496@aztec.santafe.edu>
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.gnu.franken.de/ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
next prev parent reply other threads:[~2002-11-05 7:02 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 [this message]
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
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=shd6pksdm5.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).