From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] u9fs license?
Date: Sat, 6 Jan 2001 00:40:31 -0500 [thread overview]
Message-ID: <20010106234534.EAA82199D7@mail.cse.psu.edu> (raw)
I honestly don't remember how we used to distribute u9fs, except as
packaged within a Plan 9 distribution. I've looked around a little
and can't find any other trace of it. Are you sure you found it
somewhere else? I vaguely remember we did something like the sam
release, but I can find no evidence. Can you?
Honestly, I'd be happy to give it away unfettered but I don't have
permission to do that - unless permission has already been granted.
It doesn't seem worth the local hassle of a doing a new
release/license separate from the Plan 9 one. Unless, again, it's
already been done.
If nothing comes up, I'll see if we have a paper trail in the office
files.
-rob
next reply other threads:[~2001-01-06 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 5:40 rob pike [this message]
2001-01-07 3:22 ` greg andruk
2001-01-07 5:11 ` Boyd Roberts
2001-01-08 17:09 ` ozan s. yigit
-- strict thread matches above, loose matches on Subject: below --
2001-01-06 3:20 greg andruk
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=20010106234534.EAA82199D7@mail.cse.psu.edu \
--to=rob@plan9.bell-labs.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).