From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Aug 20 license modification
Date: Mon, 9 Sep 2002 11:06:21 +0900 [thread overview]
Message-ID: <fe891544985d4336e2672fde27e47c08@granite.cias.osakafu-u.ac.jp> (raw)
I was much surprised to read those posts today, and have read the new
License at http://plan9.bell-labs.com. Yes, it's true...
I'm now rewriting Yoshitatsu's planv, which uses many codes from acme,
and I must stop my subject now. It's mostly wasted my time...
The line
>of, or in conjunction with, any other operating system
> or application.
^^^^^^^^^
made me into trouble.
Kenji
next reply other threads:[~2002-09-09 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 2:06 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-08 16:03 Skip Tavakkolian
2002-09-09 0:05 ` Jack Johnson
2002-09-08 15:48 Skip Tavakkolian
2002-09-07 19:42 Micah Stetson
2002-09-07 20:00 ` Ronald G Minnich
2002-09-08 5:27 ` Mike Haertel
2002-09-08 15:44 ` Jim Choate
2002-09-08 16:10 ` Ronald G Minnich
2002-09-09 1:38 ` 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=fe891544985d4336e2672fde27e47c08@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.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).