From: Mike Galbraith <efault@gmx.de>
To: nisus@redchan.it, "Paul G. Allen" <pgallen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, tytso@mit.edu
Subject: Re: Yes you have standing to sue GRSecurity - Yes there is a blatant violation
Date: Sun, 30 Jul 2017 17:18:46 +0200 [thread overview]
Message-ID: <1501427926.22879.92.camel@gmx.de> (raw)
In-Reply-To: <9787feb121bbbfc8035382e8bdd301b1@redchan.it>
On Sun, 2017-07-30 at 10:15 +0000, nisus@redchan.it wrote:
>
> Again, Yes I am an attorney, yes Bruce Perens is correct, Yes I know
> what I'm talking about in this field more than you American Programmers,
> no you do not know what you are talking about if you have not studied
> law.
If your motivation for posting to LKML, a technical forum, is to
dispense pro bono publico advice to hapless victims, bless you, but
LKML is not the appropriate forum. Nor is it appropriate for pro bono
advocatus, pro bono piscator, or any other conceivable variant of pro
bono discussion not ending in the latin word for kernel.
-Mike
prev parent reply other threads:[~2017-07-30 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 13:06 Yes you have standing to sue GRSecurity nisus
2017-07-29 15:32 ` Paul G. Allen
2017-07-29 20:07 ` Theodore Ts'o
2017-07-29 23:20 ` Paul G. Allen
2017-07-30 5:55 ` David Lang
2017-07-30 7:14 ` David C. Rankin
2017-07-31 14:46 ` Yes you have standing to sue GRSecurity - Two options that can be used in concert or separately nisus
2017-07-30 9:47 ` Yes you have standing to sue GRSecurity Pavel Machek
2017-07-30 9:47 ` Pavel Machek
2017-07-30 10:09 ` Yes you have standing to sue GRSecurity - Yes there is a blatant violation nisus
2017-07-30 10:15 ` nisus
2017-07-30 15:18 ` Mike Galbraith [this message]
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=1501427926.22879.92.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nisus@redchan.it \
--cc=pgallen@gmail.com \
--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