From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] webls.c - synthesize directories on the fly.
Date: Wed, 8 Oct 2003 10:09:43 +0200 [thread overview]
Message-ID: <f2c0a94991f8a5e1aed07758f65ad2ba@plan9.escet.urjc.es> (raw)
In-Reply-To: <42665.135.214.42.162.1065558632.squirrel@www.infernopark.com>
[-- Attachment #1: Type: text/plain, Size: 52 bytes --]
I'd like to get filterfs too.
thanks in any case.
[-- Attachment #2: Type: message/rfc822, Size: 3122 bytes --]
From: <vdharani@infernopark.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] webls.c - synthesize directories on the fly.
Date: Tue, 7 Oct 2003 16:30:32 -0400 (EDT)
Message-ID: <42665.135.214.42.162.1065558632.squirrel@www.infernopark.com>
Eric,
> A few years ago I wrote a filterfs exclude files matching a
> regular expression. We use it on our web site when publishing
> part of the dump file system since, as people have noted in
> the past, there can be times when you need to effectively
> delete things from Venti.
>
> It's not polished so we never put it on sources, but I'm
> willing to do so if there is sufficient interest.
I just want to know what you decided on. It would be nice if you can put it
on sources. Things like filterfs are special-purpose ones but I think it is
worth saving the code in a way it is usable when needed. Let it be there
like a parachute lying somewhere in the flight. We will use it when needed.
Thanks
dharani
next prev parent reply other threads:[~2003-10-08 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-10-08 8:45 ` arisawa
2003-10-10 7:18 ` Eric Grosse
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 12:35 Eric Grosse
2003-10-01 8:05 YAMANASHI Takeshi
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=f2c0a94991f8a5e1aed07758f65ad2ba@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).