From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] namepad
Date: Mon, 3 Feb 2003 14:01:55 -0500 [thread overview]
Message-ID: <Pine.LNX.4.30.0302031401110.10784-100000@athena> (raw)
In-Reply-To: <af4aeafd6da7a6600453e0cc5f5ddee2@plan9.bell-labs.com>
ooooh, i see.
clever bugger.
On Mon, 3 Feb 2003, David Presotto wrote:
> >What was the original intention of the namepad
> >field in the Cw struct?
> >
> >/sys/src/fs/dev/cw.c:1342 is the only line that
> >references it with the comment, `force room.'
>
> Looks to me a way ken assures that he can always
> append a /<name> on the end of the name field
> without thinking too hard about it.
>
next prev parent reply other threads:[~2003-02-03 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 18:53 David Presotto
2003-02-03 19:01 ` Sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-03 18:32 Sam
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=Pine.LNX.4.30.0302031401110.10784-100000@athena \
--to=sah@softcardsystems.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).