From: Jean Louis <bugs@gnu.support>
To: gameonlinux@redchan.it
Cc: gnu-system-discuss@gnu.org, bruce@perens.com, rms@gnu.org,
esr@thyrsus.com, torvalds@linux-foundation.org, ams@gnu.org,
linux-kernel@vger.kernel.org
Subject: Re: (Censored) Why will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)?
Date: Fri, 1 Nov 2019 08:02:58 +0100 [thread overview]
Message-ID: <20191101070258.GK3889@protected.rcdrun.com> (raw)
In-Reply-To: <e3a6a2070e2182be00b9720b4a1c591f@redchan.it>
* gameonlinux@redchan.it <gameonlinux@redchan.it> [2019-11-01 00:03]:
> I tried to send this to the list, but it was dropped as spam, which is no
> surprise since the some want to screen communications to RMS and thus
> control him.
... cut...
> Wouldn't the FSF have standing regarding the GCC plugins atleast?
> Couldn't you all rally linux-kernel copyright holders to bring a joint
> action?
>
> References:
> perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/
>
> perens.com/static/OSS_Spenger_v_Perens/0_2018cv15189/docs1/pdf/18.pdf
> (Page 10 onward of this brief gives a good recitation of the facts and
> issues
Recommended reads:
Enforcing the GNU GPL by Eben Moglen
https://www.gnu.org/philosophy/enforcing-gpl.html
and
The Principles of Community-Oriented GPL Enforcement by Joshua Gay
https://www.fsf.org/licensing/enforcement-principles
Jean
next prev parent reply other threads:[~2019-11-01 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 23:02 (Censored) Why will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)? gameonlinux
2019-11-01 7:02 ` Jean Louis [this message]
2019-11-02 0:48 ` gameonlinux
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=20191101070258.GK3889@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=ams@gnu.org \
--cc=bruce@perens.com \
--cc=esr@thyrsus.com \
--cc=gameonlinux@redchan.it \
--cc=gnu-system-discuss@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rms@gnu.org \
--cc=torvalds@linux-foundation.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