From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ide fs patch for the current plan9 version
Date: Wed, 16 May 2001 17:13:57 -0400 [thread overview]
Message-ID: <20010516211359.191B0199F3@mail.cse.psu.edu> (raw)
Yes, it is simpler to just keep the source tree clean, if you have
that option. My ex-department tried the experiment of overlaying the
contents of our file server, which we kept pretty lean, on top of the
main Plan 9 file server. It kept us current yet allowed us to
implement different administrative policies and in general substitute
our own files for those on the main file server. We didn't have
permission to clean the main source tree.
next reply other threads:[~2001-05-16 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 21:13 geoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-16 19:31 geoff
2001-05-16 21:00 ` Francisco J Ballesteros
2001-05-16 13:02 nemo
2001-05-17 4:54 ` Eric Dorman
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=20010516211359.191B0199F3@mail.cse.psu.edu \
--to=geoff@collyer.net \
--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).