From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: [9fans] a little more ftpfs
Date: Fri, 3 Jan 2003 10:06:54 +0000 [thread overview]
Message-ID: <1456643346@snellwilcox.com> (raw)
Hi,
Sorry, I diff'ed the wrong version of the file and missed this change last
night.
The below is another change to proto.c.
It asks the server use long filenames where it can (our ftp server
uses 8.3 by default and so I get Windows style munged filenames
without this change).
BTW when I synchronised against sources today I got hundreds
of directories as having been "locally modified", not really a problem
but its nice to see a short list of modified files which allows me to
check what I have fiddled with. Is there an easy way to synchronise
only these directories and not the directory's contents?
-Steve
diff /n/sources/plan9/sys/src/cmd/ip/ftpfs/proto.c proto.c
54d53
<
216a216,223
> case NetWare:
> /*
> * Request long, rather than 8.3 filenames,
> * where the Servers & Volume support them.
> */
> sendrequest("SITE LONG", nil);
> getreply(&ctlin, msg, sizeof(msg), 0);
> /* FALL THRU */
219d225
< case NetWare:
next reply other threads:[~2003-01-03 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 10:06 steve.simon [this message]
2003-01-03 13:38 ` David Presotto
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=1456643346@snellwilcox.com \
--to=steve.simon@snellwilcox.com \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).