linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: lrosen@rosenlaw.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org, kcopenhaver@choate.com,
	Richard Fontana <rfontana@redhat.com>,
	Marc Fleischmann <mwf@risingtidesystems.com>,
	Nicholas Bellinger <nab@risingtidesystems.com>,
	alan@lxorguk.ukuu.org.uk, bkuhn@sfconservancy.org, tytso@mit.edu,
	andy@groveronline.com
Subject: Re: scsi target, likely GPL violation
Date: Thu, 15 Nov 2012 10:21:00 -0800	[thread overview]
Message-ID: <50A5328C.800@redhat.com> (raw)
In-Reply-To: <14c701cdc059$d6fd28b0$84f77a10$@rosenlaw.com>

Hi all,

First, I do not, and did not, have access to the proprietary OS, which
has been referred to. Otherwise, I would have checked it.

Second, I appreciate that my questions and tentative inferences may not
have been perfect, given that I did not have the complete facts, but I
did try to obtain them from RTS before raising questions in this forum.
But I was not successful.

Third, in retrospect, I think a more measured approach to the dialog
may have been a better course. I am interested in understanding the
situation. My primary goal was to avoid duplicating a lot of work, if
RTS plans to open-source the new features they have added to the
proprietary version.

Fourth, my questions about the GPL’s requirements in this context remain.

Finally, I was, in this thread, speaking on my behalf alone and
at my initiative-- not Red Hat’s, as some may have incorrectly
concluded. I'll be using a personal email account (CC'd) for this issue
in the future, in order to make this more explicit.

Regards -- Andy

  parent reply	other threads:[~2012-11-15 18:21 UTC|newest]

Thread overview: 28+ 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
2012-11-09 20:26                 ` Alan Cox
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-15 18:21                 ` Andy Grover [this message]
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=50A5328C.800@redhat.com \
    --to=agrover@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andy@groveronline.com \
    --cc=bkuhn@sfconservancy.org \
    --cc=kcopenhaver@choate.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lrosen@rosenlaw.com \
    --cc=mwf@risingtidesystems.com \
    --cc=nab@risingtidesystems.com \
    --cc=rfontana@redhat.com \
    --cc=target-devel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).