From: Chris Richards <gizmo@giz-works.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] SELinux policy for nginx, or include in apache?
Date: Tue, 21 Jun 2011 16:27:07 -0500 [thread overview]
Message-ID: <1308691636.25895.2.camel@chris.localhost> (raw)
In-Reply-To: <20110619151944.GB4651@siphos.be>
On Sun, 2011-06-19 at 17:19 +0200, Sven Vermeulen wrote:
> On Wed, Jun 15, 2011 at 10:15:14PM -0500, Chris Richards wrote:
> > I'm torn on this, but basically I think we ought to track upstream here.
>
> Which is... ? ;-)
Well, it looked to me like Christopher pretty much squashed the patch,
for reasons already discussed there. For reasons that I've already
mentioned, my opinion is that we should steer clear of it, at least for
now. Of course, that's just my opinion. ;)
next prev parent reply other threads:[~2011-06-21 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 17:45 [gentoo-hardened] SELinux policy for nginx, or include in apache? Sven Vermeulen
2011-06-15 20:08 ` Francisco Blas Izquierdo Riera (klondike)
2011-06-16 0:40 ` Anthony G. Basile
2011-06-16 3:15 ` Chris Richards
2011-06-19 15:19 ` Sven Vermeulen
2011-06-21 21:27 ` Chris Richards [this message]
2011-06-21 21:27 ` Chris Richards
2011-06-19 15:15 ` Sven Vermeulen
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=1308691636.25895.2.camel@chris.localhost \
--to=gizmo@giz-works.com \
--cc=gentoo-hardened@lists.gentoo.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