From: Andy Grover <agrover@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: nab@risingtidesystems.com,
Chris Friesen <chris.friesen@genband.com>,
Jon Mason <jdmason@kudzu.us>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Marc Fleischmann <mwf@risingtidesystems.com>
Subject: Re: scsi target, likely GPL violation
Date: Fri, 09 Nov 2012 11:52:19 -0800 [thread overview]
Message-ID: <509D5EF3.9030809@redhat.com> (raw)
In-Reply-To: <20121109110336.41833034@pyramind.ukuu.org.uk>
On 11/09/2012 03:03 AM, Alan Cox wrote:
> I fail to understand the maintainer question however. If you were trying
> to block people adding target features that competed that would be a
> different thing.
You think it's ok for us to have an unrepentant GPL violator as a
subsystem maintainer??
If that's really what you're saying then I think that's crazy.
-- Andy
next prev parent reply other threads:[~2012-11-09 19:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 16:50 scsi target, likely GPL violation Andy Grover
2012-11-08 1:02 ` Jon Mason
2012-11-08 1:57 ` Chris Friesen
2012-11-08 16:57 ` Andy Grover
2012-11-08 20:05 ` Nicholas A. Bellinger
2012-11-08 20:22 ` Dave Airlie
2012-11-08 21:22 ` Andy Grover
2012-11-09 2:08 ` Nicholas A. Bellinger
2012-11-09 11:03 ` Alan Cox
2012-11-09 19:52 ` Andy Grover [this message]
2012-11-09 20:26 ` Alan Cox
2012-11-11 22:13 ` Lawrence Rosen
2012-11-11 22:13 ` Lawrence Rosen
2012-11-11 22:41 ` Julian Calaby
2012-11-11 23:03 ` Dave Airlie
2012-11-12 14:21 ` Bradley M. Kuhn
2012-11-12 14:21 ` Bradley M. Kuhn
2012-11-15 18:21 ` Andy Grover
2012-11-09 23:16 ` Andy Grover
2012-11-10 23:32 ` Bradley M. Kuhn
2012-11-08 16:57 ` Andy Grover
2012-11-11 9:34 ` James Bottomley
2012-11-11 13:05 ` Theodore Ts'o
2012-11-11 15:15 ` Bradley M. Kuhn
2012-11-11 18:22 ` James Bottomley
2012-11-11 18:32 ` Alan Cox
2012-11-14 2:32 ` James Bottomley
2012-11-12 14:08 ` Theodore Ts'o
2012-11-12 14:15 ` Alan Cox
2012-11-12 0:39 ` Douglas Gilbert
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=509D5EF3.9030809@redhat.com \
--to=agrover@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris.friesen@genband.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mwf@risingtidesystems.com \
--cc=nab@risingtidesystems.com \
--cc=target-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.