From: Michael Albinus <michael.albinus@gmx.de>
To: "Eric Klaus" <etklaus@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Ange-ftp: Getting files with no extension on dumb hosts
Date: Fri, 10 Oct 2008 14:20:07 +0200 [thread overview]
Message-ID: <87prm8skug.fsf@alcatel-lucent.de> (raw)
In-Reply-To: <612c9da00810090811p541fb238g14ddba0006d62a5b@mail.gmail.com> (Eric Klaus's message of "Thu, 9 Oct 2008 10:11:03 -0500")
"Eric Klaus" <etklaus@gmail.com> writes:
> I suppose that this error message means that I'm going to have to roll my
> own set of commands for this particularly dumb host? I believe my host is an
> AS/400; I'm not sure why it seems to have such lackluster ftp support.
Likely, you must do it yourself. I'd help you, but I have no access on
such a machine.
Best regards, Michael.
prev parent reply other threads:[~2008-10-10 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 21:41 Ange-ftp: Getting files with no extension on dumb hosts Eric
2008-10-09 7:20 ` Michael Albinus
2008-10-09 14:21 ` Eric Klaus
2008-10-09 14:25 ` Michael Albinus
2008-10-09 15:11 ` Eric Klaus
2008-10-10 12:20 ` Michael Albinus [this message]
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=87prm8skug.fsf@alcatel-lucent.de \
--to=michael.albinus@gmx.de \
--cc=etklaus@gmail.com \
--cc=help-gnu-emacs@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.
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).