From: "Martin Jost" <Martin.Jost@siemens.com>
Subject: Re: Obtaining 21.3
Date: Thu, 18 Sep 2003 13:19:03 +0200 [thread overview]
Message-ID: <bkc4b8$4s7$1@news.mch.sbs.de> (raw)
In-Reply-To: mailman.381.1063875673.21628.help-gnu-emacs@gnu.org
<ray@nabuli.de> schrieb im Newsbeitrag news:mailman.381.1063875673.21628.help-gnu-emacs@gnu.org...
> On Thu, 18 Sep 2003, Florian Lindner wrote:
>
> > since 21.3 is not available on the GNU server for more than 2 months
> > now, is there trustworthy source where I can get Emacs 21.3?
> Oh, and by the way: Is it worth the trouble to upgrade from 21.2.1?
Since it has been probably removed for a reason, the answer is probably: NO.
I stepped back from 21.3. to 21.2. after massive problems with emacs-hangs after killing emacs-buffers.
Usually emacs hung some three times a day..... (on HPUX 10.20, compiled with HP-tools)
So I stepped back to 21.2 which doesn't show the problem.
Could some knowledgeable person shed some light on the reasons for the removal of 21.3. from the ftp-servers ?
Martin
next prev parent reply other threads:[~2003-09-18 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 7:56 Obtaining 21.3 Florian Lindner
2003-09-18 8:52 ` ray
[not found] ` <mailman.381.1063875673.21628.help-gnu-emacs@gnu.org>
2003-09-18 11:19 ` Martin Jost [this message]
2003-09-18 12:37 ` Uwe Siart
2003-09-18 16:07 ` Kevin Rodgers
2003-09-19 12:39 ` Martin Jost
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 15:39 Enabling global-font-lock-mode Florian Lindner
2002-10-24 15:43 ` Phillip Lord
2002-10-24 16:49 ` John McCabe
2002-10-24 18:11 ` Florian Lindner
2002-10-25 9:42 ` John McCabe
2002-10-25 14:27 ` Stefan Monnier <foo@acm.com>
[not found] ` <Florian.Lindner@xgm.de>
2002-10-24 17:40 ` Peter S Galbraith
2003-09-25 17:00 ` Obtaining 21.3 Peter S Galbraith
[not found] ` <mailman.1035481346.8205.help-gnu-emacs@gnu.org>
2002-10-27 22:24 ` Enabling global-font-lock-mode Tim Cross
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='bkc4b8$4s7$1@news.mch.sbs.de' \
--to=martin.jost@siemens.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).