From: paul.moore@hp.com (paul.moore at hp.com)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [RFC PATCH v1] network: Enable "network_peer_controls" and fix some remaining issues
Date: Mon, 08 Dec 2008 14:53:59 -0500 [thread overview]
Message-ID: <20081208195409.080889391@flek.lan> (raw)
An embedded and charset-unspecified text was scrubbed...
Name: network-in_out_basic
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20081208/862b53b7/attachment.pl
next reply other threads:[~2008-12-08 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 19:53 paul.moore at hp.com [this message]
2008-12-08 20:37 ` [refpolicy] [RFC PATCH v1] network: Enable "network_peer_controls" and fix some remaining issues Paul Moore
2008-12-08 20:41 ` Paul Moore
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=20081208195409.080889391@flek.lan \
--to=paul.moore@hp.com \
--cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.