From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] webls.c - synthesize directories on the fly.
Date: Wed, 1 Oct 2003 17:05:56 +0900 [thread overview]
Message-ID: <8822f5d6871b810fee4cdcc1a65bdb49@orthanc.cc.titech.ac.jp> (raw)
On Wed Oct 1 14:47:34 JST 2003, Lucio De Re wrote:
> Bind(1) does not have an "exclude" function that I can know of,
> which means that exclusions can only be effected by enumerating
> the inclusions. This can get extremely tedious.
ten points for Griffindor. i neglected the case
that fine grained access control is necessary.
Thank you for your replies.
--
next reply other threads:[~2003-10-01 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 8:05 YAMANASHI Takeshi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 12:35 Eric Grosse
2003-10-01 5:21 YAMANASHI Takeshi
2003-10-01 5:39 ` Dan Cross
2003-10-01 5:41 ` Lucio De Re
2003-10-01 11:41 ` Eric Grosse
2003-10-01 16:17 ` Dan Cross
2003-10-07 20:30 ` vdharani
2003-10-08 8:09 ` Fco.J.Ballesteros
2003-10-08 8:45 ` arisawa
2003-10-10 7:18 ` Eric Grosse
2003-09-29 6:14 cross
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=8822f5d6871b810fee4cdcc1a65bdb49@orthanc.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.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).