From: Al Viro <viro@ftp.linux.org.uk>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Constantine A. Murenin" <mureninc@gmail.com>,
Jeff Garzik <jeff@garzik.org>, Jason Dixon <jason@dixongroup.net>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, jirislaby@gmail.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: That whole "Linux stealing our code" thing
Date: Sun, 2 Sep 2007 02:53:56 +0100 [thread overview]
Message-ID: <20070902015356.GO21089@ftp.linux.org.uk> (raw)
In-Reply-To: <43e72e890709011842m213b590ds141deb9657b979e7@mail.gmail.com>
On Sat, Sep 01, 2007 at 09:42:54PM -0400, Luis R. Rodriguez wrote:
> We asked SFLC to work with us to make sure that everyone's copyrights
> were respected in the right places, and that the licenses various developers
> wanted for their copyrights were implemented correctly. The patch I sent
> implements SFLC's suggestions in that regard.
You know, I'm rapidly losing any respect to both sides of that. Eben
Moglen as source of advice in "is it OK to convert to GPL-only"? And
you seriously rely on morality of that? Theo's rants aside, if you
have to rely on SFLC for licensing decisions... Ouch.
next prev parent reply other threads:[~2007-09-02 1:54 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200709010140.l811eq9H005896@cvs.openbsd.org>
2007-09-01 16:48 ` Fwd: That whole "Linux stealing our code" thing Constantine A. Murenin
2007-09-01 17:21 ` Jeff Garzik
2007-09-01 17:37 ` Constantine A. Murenin
2007-09-01 20:54 ` Adrian Bunk
2007-09-01 21:16 ` Adrian Bunk
2007-09-01 21:51 ` Constantine A. Murenin
2007-09-01 22:06 ` Adrian Bunk
2007-09-01 21:27 ` Constantine A. Murenin
2007-09-01 21:52 ` Adrian Bunk
2007-09-01 23:29 ` Constantine A. Murenin
2007-09-01 23:48 ` Luis R. Rodriguez
2007-09-02 0:11 ` Constantine A. Murenin
2007-09-02 0:09 ` Adrian Bunk
2007-09-02 0:53 ` Constantine A. Murenin
2007-09-02 10:36 ` Alan Cox
2007-09-02 11:20 ` Igor Sobrado
2007-09-02 11:50 ` Adrian Bunk
2007-09-02 12:28 ` Igor Sobrado
2007-09-02 12:36 ` Jeff Garzik
2007-09-02 12:46 ` Alan Cox
2007-09-02 13:00 ` Igor Sobrado
2007-09-02 13:12 ` Adrian Bunk
2007-09-02 13:53 ` Alan Cox
2007-09-02 13:57 ` Krzysztof Halasa
2007-09-02 14:11 ` Jeff Garzik
2007-09-02 15:58 ` Igor Sobrado
2007-09-02 18:23 ` Matthew Jacob
2007-09-02 18:21 ` Al Viro
2007-09-02 12:36 ` Alan Cox
2007-09-02 0:36 ` Jason Dixon
2007-09-02 1:34 ` Jeff Garzik
2007-09-02 1:39 ` Constantine A. Murenin
2007-09-02 1:42 ` Luis R. Rodriguez
2007-09-02 1:53 ` Al Viro [this message]
2007-09-02 1:43 ` Jeff Garzik
2007-09-02 1:58 ` Casey Dahlin
2007-09-02 2:06 ` Al Viro
2007-09-02 2:44 ` Jason Dixon
2007-09-02 1:55 ` Adrian Bunk
2007-09-02 3:47 ` Valdis.Kletnieks
2007-09-02 5:09 ` Constantine A. Murenin
2007-09-02 5:46 ` Valdis.Kletnieks
2007-09-02 2:22 ` Jonathan Gray
2007-09-02 10:18 ` Alan Cox
2007-09-01 22:03 ` Fwd: " Sam Leffler
2007-09-01 22:29 ` Adrian Bunk
2007-09-01 20:30 ` Alan Cox
2007-09-01 20:57 ` Jacob Meuser
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=20070902015356.GO21089@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jason@dixongroup.net \
--cc=jeff@garzik.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mureninc@gmail.com \
--cc=netdev@vger.kernel.org \
/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).