From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: ftpfs change to compensate for some servers
Date: Fri, 10 Nov 1995 11:16:49 -0500 [thread overview]
Message-ID: <19951110161649.PQ2PtBfEpQ6V-BbwUsCg2c00ZL0tlwId9SDCZKWl-9I@z> (raw)
>>I think this is easier and more correct since it covers all systems, not
>>just Unix-like:
i agree. if a non-Unix system ever decided to
use . or .. as a file name, it would have to
be mapped to something else anyhow.
next reply other threads:[~1995-11-10 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-10 16:16 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-10 8:58 presotto
1995-11-09 20:02 forsyth
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19951110161649.PQ2PtBfEpQ6V-BbwUsCg2c00ZL0tlwId9SDCZKWl-9I@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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 NNTP newsgroup(s).