From: Yoann Vandoorselaere <yoann@mandrakesoft.com>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New tree started ;)
Date: 01 Jan 2002 12:01:49 +0100 [thread overview]
Message-ID: <1009882909.2559.76.camel@alph> (raw)
In-Reply-To: <3C318DCE.8020105@drugphish.ch>
In-Reply-To: <1009835143.7667.0.camel@ohdarn.net> <3C318DCE.8020105@drugphish.ch>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Tue, 2002-01-01 at 11:22, Roberto Nibali wrote:
> Hello Michael,
>
> Thanks for doing this. Could you tell me which criteria you have to
> choose patches to go in? I see grsecurity in the to be merged queue
> which is not likely to ever go into 2.4.x. It's more likely to be
> converted to the LSM framework (parts of it if still needed) and then
> integrated into 2.5.x.
AFAICT, the grsecurity patch include the Solar Designer non executable
patch. And AFAICT, this one won't be included in the main kernel tree.
My point is that this patch is against previously taken decision. So why
would it be included in such a tree ?
[...]
--
Yoann Vandoorselaere
http://www.prelude-ids.org
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-01-01 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 21:45 New tree started ;) Michael Cohen
2001-12-31 22:07 ` William Lee Irwin III
2002-01-02 16:09 ` george anzinger
2002-01-01 10:22 ` Roberto Nibali
2002-01-01 11:01 ` Yoann Vandoorselaere [this message]
[not found] <Pine.LNX.4.33.0112311415110.16124-100000@svr.cih.com>
2001-12-31 22:37 ` Michael Cohen
[not found] <200201012342.PAA14236@cesium.transmeta.com>
2002-01-02 2:18 ` Michael Cohen
2002-01-02 2:24 ` H. Peter Anvin
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=1009882909.2559.76.camel@alph \
--to=yoann@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
/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