From: "David Schwartz" <davids@webmaster.com>
To: <rjd@xyzzy.clara.co.uk>, "Stuart MacDonald" <stuartm@connecttech.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Re: Microsoft begining to open source Windows 2000?
Date: Thu, 8 Mar 2001 14:46:41 -0800 [thread overview]
Message-ID: <024001c0a822$5f4844a0$7c4cf9d1@geeksparadise.com> (raw)
In-Reply-To: <200103081738.f28HcDC03173@xyzzy.clara.co.uk>
> > It seems to me this might be an opportunity...
>
> Or a trap. I'm not about to go anywhere near this and won't even look at
> the licience but I bet the M$ argument will go something like:
>
> You've looked at the code.
> You now know things that are propriatary to M$.
> You are not allowed to apply it to anything outside M$.
> Stop working on those free sources the forbidden knowledge might leak.
> You have me assimilated.
If you're really worried, have the person with access to the MS code
write a patch, and then have someone without access to the MS code
reimplement the patch. Make sure that all that is taken from the orignially
written patch are ideas and algorithms, not actual code.
Of course, you would still have to carefully read the actual license
before deciding on the correct isolation scheme.
DS
next prev parent reply other threads:[~2001-03-08 22:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 15:01 Venkatesh Ramamurthy
2001-03-08 15:52 ` Mohammad A. Haque
2001-03-08 16:06 ` Alan Cox
2001-03-09 5:43 ` J. Dow
2001-03-09 6:34 ` Mike Galbraith
2001-03-09 11:11 ` Dr. Michael Weller
2001-03-08 17:21 ` [OT] " Stuart MacDonald
2001-03-08 17:38 ` rjd
2001-03-08 22:46 ` David Schwartz [this message]
2001-03-08 17:40 ` James A. Sutherland
2001-03-08 19:30 ` Nathan Paul Simons
2001-03-08 19:10 ` Roeland Th. Jansen
2001-03-08 19:38 ` Lars Gaarden
2001-03-09 18:16 ` Kai Henningsen
2001-03-10 3:49 ` Steve Underwood
2001-03-11 17:23 ` Mark H. Wood
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='024001c0a822$5f4844a0$7c4cf9d1@geeksparadise.com' \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjd@xyzzy.clara.co.uk \
--cc=stuartm@connecttech.com \
/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
all inboxes | Powered by JetHome®