From: pemente@northpark.edu (Eric Pement)
Subject: Re: Q: status of EmacsNT 21.3 binaries
Date: 26 Nov 2003 08:26:00 -0800 [thread overview]
Message-ID: <227a55e9.0311260826.6e347313@posting.google.com> (raw)
In-Reply-To: mailman.547.1069744599.399.help-gnu-emacs@gnu.org
Eli Zaretskii <eliz@elta.co.il> wrote in message news:<mailman.547.1069744599.399.help-gnu-emacs@gnu.org>...
> > From: pemente@northpark.edu (Eric Pement)
> > Newsgroups: gnu.emacs.help
> > Date: 24 Nov 2003 19:28:11 -0800
> >
> > I've been waiting for the GNU Emacs 21.3 binaries for WinNT to be
> > released for quite some time, and the ftp sites at GNU org and the
> > mirrors still do not have anything available, except the promise that
> > it's coming RSN (Real Soon Now).
[ ... ]
> This isn't the proper place to post this. The problem lies with the
> gnu.org sysadmins, as the tarballs were prepared by the NTEmacs
> maintainer several weeks ago, but mere mortals are not allowed to put
> things on ftp.gnu.org, for fear of malicious hackers.
>
> So I suggest you post this on bug-gnu-emacs@gnu.org or write directly
> to Richard Stallman <rms@gnu.org>. He would then prod the gnu.org
> sysadmins, I hope.
I did write to RMS, and he replied promptly but tersely that he
doesn't have anything to do with making or distributing Windows
binaries. He didn't say who *does* distribute those binaries.
However, your reference to the bug-gnu-emacs email address got me
thinking, so I visited the gnu.emacs.bug newsgroup, and found this
message posted yesterday by Kevin Rodgers:
---
Jason Rumney sent me the precompiled Windows binaries for Emacs 21.3:
4402129 Nov 11 00:07 emacs-21.3-barebin-i386.tar.gz
13842323 Nov 11 00:55 emacs-21.3-bin-i386.tar.gz
19473545 Nov 11 00:06 emacs-21.3-fullbin-i386.tar.gz
3993557 Nov 11 00:06 emacs-21.3-leim.tar.gz
7138900 Nov 11 00:04 emacs-21.3-lisp.tar.gz
1854180 Nov 11 00:06 emacs-21.3-undumped-i386.tar.gz
and I put them on ftp://fly.cnuce.cnr.it/pub/tmp/. He already sent
signatures to the maintainers list.
---
Thanks, Kevin and Eli, for your help with my question. I got the file.
next prev parent reply other threads:[~2003-11-26 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 3:28 Q: status of EmacsNT 21.3 binaries Eric Pement
2003-11-25 6:16 ` Eli Zaretskii
[not found] ` <mailman.547.1069744599.399.help-gnu-emacs@gnu.org>
2003-11-26 16:26 ` Eric Pement [this message]
2003-11-26 17:32 ` Kevin Rodgers
2003-11-26 18:47 ` Eli Zaretskii
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=227a55e9.0311260826.6e347313@posting.google.com \
--to=pemente@northpark.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.
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).