From: Greg KH <greg@kroah.com>
To: Linus Turdvals <turdvals@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
rdunlap@xenotime.net, security@kernel.org
Subject: Re: [Security] [PATCH] Update security bugs policy in Documentation/SecurityBugs
Date: Mon, 1 Jun 2009 13:58:48 -0700 [thread overview]
Message-ID: <20090601205848.GA28705@kroah.com> (raw)
In-Reply-To: <d32c60160906011141y22299f2cwd3df46f6e26cf33d@mail.gmail.com>
On Mon, Jun 01, 2009 at 08:41:16PM +0200, Linus Turdvals wrote:
> This patch updates the security bugs handling policy in
> Documentation/SecurityBugs, to match with the current practices
> and philosophy of the Linux kernel security team.
>
> Please apply to avoid the masturbating monkeys in the security
> circus from reporting misleading bugs with no security impact
> whatsoever.
>
> Signed-off-by: Linus Turdvalds <turdvals@gmail.com>
*plonk*
prev parent reply other threads:[~2009-06-01 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 18:41 [PATCH] Update security bugs policy in Documentation/SecurityBugs Linus Turdvals
2009-06-01 20:58 ` Greg KH [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=20090601205848.GA28705@kroah.com \
--to=greg@kroah.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=security@kernel.org \
--cc=turdvals@gmail.com \
/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