From: linuxgpletc@redchan.it
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Ivan Ivanov <qmastery16@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
gentoo-user@lists.gentoo.org, freebsd-chat@freebsd.org,
misc@openbsd.org, rms@gnu.org
Subject: Re: GRSec is vital to Linux security -- SFConservancy = legal malpractice. Use own lawyer.
Date: Thu, 24 Jan 2019 16:31:08 +0000 [thread overview]
Message-ID: <755ebf4887176797356a1e0b73df64c6@redchan.it> (raw)
In-Reply-To: <3efc6268-747d-0841-4249-5804fa9095ca@metux.net>
One note: If you are going to defend your copyrights and the idea of the
GPL, do not rely on the "free software legal groups".
The "free software legal groups" exist only to commit legal malpractice.
The guy who ran the SFConservancy (Bradly Kuhn IIRC) isn't even a
lawyer. He advises "clients" to wait it out: AKA run down the
statute-of-limitations so you have no case.
A fucking _FAGGOT_.
You cannot rely on the "Free software legal groups" to help you because
_they do not exist_.
Only recently did the SFConservancy hire a lawyer, and they had to put
her in the head position because Bar rules do not allow a lawyer to be
below non-lawyers in a legal firm.
Just wanted to let you know.
next prev parent reply other threads:[~2019-01-24 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 18:19 GRSec is vital to Linux security linuxgpletc
2019-01-23 20:46 ` Ivan Ivanov
2019-01-23 22:28 ` linuxgpletc
2019-01-24 15:31 ` Enrico Weigelt, metux IT consult
2019-01-24 16:03 ` Adam Borowski
2019-01-24 16:22 ` linuxgpletc
2019-01-24 16:31 ` linuxgpletc [this message]
2019-01-24 16:40 ` Fwd: " linuxgpletc
2019-01-28 20:20 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission linuxgpletc
2019-01-29 8:51 ` linuxgpletc
2019-01-29 9:10 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update) linuxgpletc
2019-01-29 9:38 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update 3) linuxgpletc
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=755ebf4887176797356a1e0b73df64c6@redchan.it \
--to=linuxgpletc@redchan.it \
--cc=freebsd-chat@freebsd.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=misc@openbsd.org \
--cc=qmastery16@gmail.com \
--cc=rms@gnu.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).