From: kokamoto@hera.eonet.ne.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] changing close()
Date: Sat, 27 Aug 2005 17:02:37 +0900 [thread overview]
Message-ID: <59f6243a5c1ad89ccb793e84a4db84e0@hera.eonet.ne.jp> (raw)
In-Reply-To: <224bdf80645117e6614adf0731299f59@terzarima.net>
>>>IL being long gone, all that
>
> i use it all the time, even across boundaries.
I'm doing it too at work. Geoff's 64bit Ken's fileserver began to work.
Thanks Geoff, it's very nice, I can use long file names there.
Kenji -- from home
next prev parent reply other threads:[~2005-08-27 8:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 12:06 Ronald G Minnich
2005-08-16 8:07 ` Scott Schwartz
2005-08-16 19:56 ` Charles Forsyth
2005-08-16 23:08 ` Derek Fawcus
2005-08-16 8:58 ` Charles Forsyth
2005-08-16 17:19 ` Brantley Coile
2005-08-21 20:17 ` Russ Cox
2005-08-23 8:28 ` Ronald G Minnich
2005-08-23 16:19 ` Charles Forsyth
2005-08-23 9:03 ` Ronald G Minnich
2005-08-23 16:54 ` Charles Forsyth
2005-08-27 8:02 ` kokamoto [this message]
2005-08-27 8:26 ` kokamoto
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=59f6243a5c1ad89ccb793e84a4db84e0@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--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).