[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D81EA0BC-AD13-4C6B-943B-80B5FE355E56@dixongroup.net>
Date: Sat, 1 Sep 2007 22:44:16 -0400
From: Jason Dixon <jason@...ongroup.net>
To: Casey Dahlin <cjdahlin@...u.edu>
Cc: "Constantine A. Murenin" <mureninc@...il.com>,
Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
jirislaby@...il.com, alan@...rguk.ukuu.org.uk
Subject: Re: That whole "Linux stealing our code" thing
On Sep 1, 2007, at 9:58 PM, Casey Dahlin wrote:
> Suppose you saw some other variant of *nix that had some code you
> wanted to use, but there was a gaping security hole in it. Wouldn't
> you patch it before you incorporated it? and would it be your fault
> if this fix made the code not work with the original?
>
> We took the code and fixed a gaping security vulnerability that
> appeared within the opening comment. We DO care who does what with
> our code, and we fully intend to cover our balls.
Since when is this *your* code? Oh that's right, when Jiri decided
to steal it by deleting Reyk's copyright and license. Oh wait,
that's already been corrected. What was your point again?
> The problem is yours to fix. If you actually care, use a license
> that SAYS you care. Right now there's a big /* I don't give a shit
> */ on top of every BSD file. We took you at your word and assumed
> you didn't. Now its too late and you suddenly care, don't you?
The BSD license, in effect, says that we care about good code. We
allow anyone to use it. The only stipulation is that the copyright
and license permissions must remain intact.
Are you trying to be hateful, or are you really this ignorant?
---
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists