From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>,
"Theodore Ts'o" <tytso@mit.edu>, Andy Grover <agrover@redhat.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
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>,
Nicholas Bellinger <nab@risingtidesystems.com>
Subject: Re: scsi target, likely GPL violation
Date: Tue, 13 Nov 2012 18:32:54 -0800 [thread overview]
Message-ID: <1352860374.28921.3.camel@dabdike> (raw)
In-Reply-To: <20121111183243.62602d9b@pyramind.ukuu.org.uk>
On Sun, 2012-11-11 at 18:32 +0000, Alan Cox wrote:
> > > 1. Yes, I've got first hand proof of a GPL violation (in which case
> > > we'll then move to seeing how we can remedy this) or
> > > 2. A genuine public apology for the libel, which I'll do my best to
> > > prevail on RTS to accept.
> > >
> > > Because any further discussion of unsubstantiated allegations of this
> > > nature exposes us all to jeopardy of legal sanction.
> >
> > That asks for moderation until we have a better investigation of the
> > facts. It definitely doesn't try to prejudge them or express preference
> > for a specific outcome as your misquote makes out.
>
> So how can you demand a public apology for libel or instant first hand
> proof and now claim you just wanted moderation ? It's not hard to see why
> your position was misinterpreted ?
So you want me to be less definite to avoid misinterpretation?
OK, here it is: I'd really appreciate it if there was more rigour
behind the initial investigation before going public with suspicions of
GPL violation. Based on what I read on the internet is a bit too low a
bar for me, particularly when, I believe, Red Hat has the proprietary
target OS and can check directly.
We now have a whole runaway train of suspicion and lawyer involvement
before anyone has actually confirmed there is a problem.
James
next prev parent reply other threads:[~2012-11-14 7:03 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
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 [this message]
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=1352860374.28921.3.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=agrover@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bkuhn@sfconservancy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mwf@risingtidesystems.com \
--cc=nab@linux-iscsi.org \
--cc=nab@risingtidesystems.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).