From: Richard Stallman <rms@gnu.org>
Cc: Lute.Kamstra@cwi.nl, emacs-devel@gnu.org
Subject: Re: Emacs 21.3 tarballs.
Date: Thu, 02 Oct 2003 23:37:50 -0400 [thread overview]
Message-ID: <E1A5GlK-0000ZF-Vh@fencepost.gnu.org> (raw)
In-Reply-To: <E1A4oWm-0004DM-00@pot.cnuce.cnr.it> (message from Francesco Potorti` on Wed, 01 Oct 2003 23:28:56 +0200)
>If so, maybe you could put them on the ftp server again?
I'll do that immediately, if I don't find any problems accessing the gnu
machines. I was not aware of this problem. I'l let you know when I'm
finished.
Thank you!
next prev parent reply other threads:[~2003-10-03 3:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 20:53 Emacs 21.3 tarballs Lute Kamstra
2003-10-01 21:28 ` Francesco Potorti`
2003-10-03 3:37 ` Richard Stallman [this message]
2003-10-01 22:01 ` Francesco Potorti`
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=E1A5GlK-0000ZF-Vh@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=Lute.Kamstra@cwi.nl \
--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).