public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: trond.myklebust@fys.uio.no, Christoph Hellwig <hch@infradead.org>,
	Bill Davidsen <davidsen@tmr.com>,
	Guillaume Boissiere <boissiere@adiglobal.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6] The List, pass #2
Date: Wed, 31 Jul 2002 19:42:52 -0400	[thread overview]
Message-ID: <20020731234252.GA14930@fieldses.org> (raw)
In-Reply-To: <1028161904.13048.20.camel@irongate.swansea.linux.org.uk>

On Thu, Aug 01, 2002 at 01:31:44AM +0100, Alan Cox wrote:
> On Wed, 2002-07-31 at 21:34, Trond Myklebust wrote:
> > Care to comment on why it is not GPL compatible? Given that they are
> > interested in merging their code into the standard kernel ASAP, I know
> > that they'd be interested in correcting any incompatibilities.
> 
> The 3 clause BSD though very much a completely free/open license has
> requirements conflicting with the GPL 
> 
> http://www.fsf.org/licenses/license-list.html#GPLIncompatibleLicenses
> http://www.fsf.org/philosophy/bsd.html

The "original BSD license" listed on that page actually has 4 numbered
clauses, number 3 (the "advertising clause") being the conflicting one.
The "modified BSD license", which they link to on the same page, has 3
clauses and *is* GPL compatible.  As far as I can tell, the license we are
using at CITI is nearly word-for-word the "modified BSD license", and is
GPL compatible.

--Bruce Fields

  reply	other threads:[~2002-07-31 23:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19  4:47 [2.6] The List, pass #2 Guillaume Boissiere
2002-07-19  5:08 ` Karim Yaghmour
2002-07-19 12:41 ` mbs
2002-07-19 13:16 ` jlnance
2002-07-20  7:28 ` Bruce Harada
2002-07-28 10:47 ` Aaron Lehmann
2002-07-31 17:43 ` Bill Davidsen
2002-07-31 17:58   ` Christoph Hellwig
2002-07-31 18:54     ` Bill Davidsen
2002-07-31 20:20     ` Trond Myklebust
2002-07-31 20:23       ` Christoph Hellwig
2002-07-31 20:24         ` Christoph Hellwig
2002-07-31 20:34         ` Trond Myklebust
2002-08-01  0:31           ` Alan Cox
2002-07-31 23:42             ` J. Bruce Fields [this message]
2002-08-01  9:33             ` David Schwartz
2002-08-01 13:42               ` Alan Cox
2002-08-01 15:39                 ` J. Bruce Fields
2002-07-31 22:04   ` David Lang
2002-08-01  9:33     ` Helge Hafting
2002-08-03  3:40       ` Pavel Machek
2002-08-08  9:02         ` Helge Hafting
2002-08-13  3:00           ` Bill Davidsen
2002-08-13  5:27           ` H. Peter Anvin
2002-08-01  0:34   ` Neil Brown
2002-08-01  1:56 ` Albert D. Cahalan
2002-08-01  2:30   ` Roland Dreier
2002-08-01  3:25     ` Albert D. Cahalan
2002-08-01  4:05       ` Roland Dreier
2002-08-01  5:08   ` Linus Torvalds
2002-08-01  6:10     ` Austin Gonyou
2002-08-05  7:29       ` Rob Landley
2002-08-01 18:45     ` Ben Greear
2002-08-01 14:12   ` Alan Cox
2002-08-09  2:30 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-08-07 17:11 Matt_Domsch

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=20020731234252.GA14930@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=boissiere@adiglobal.com \
    --cc=davidsen@tmr.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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