From: Joshua Brindle <jbrindle@tresys.com>
To: dwalsh@redhat.com
Cc: cpebenito@tresys.com, selinux@tycho.nsa.gov
Subject: Re: reference policy mailing list (was [PATCH] refpolicy: system_udev changes including brctl policy. Mostly xen related)
Date: Thu, 02 Aug 2007 15:50:06 -0400 [thread overview]
Message-ID: <46B2356E.8040706@tresys.com> (raw)
In-Reply-To: <200708021816.l72IGxVT022810@redsox.boston.devel.redhat.com>
dwalsh@redhat.com wrote:
This is just a friendly suggestion, would it be possible to have a
refpolicy list that is separate from the selinux list for refpolicy
updates? I only ask because refpolicy gets so many updates and is
possibly interesting to a different set of people than those interested
in SELinux development.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2007-08-02 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 18:16 [PATCH] refpolicy: system_udev changes including brctl policy. Mostly xen related dwalsh
2007-08-02 19:50 ` Joshua Brindle [this message]
2007-09-05 17:47 ` Christopher J. PeBenito
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=46B2356E.8040706@tresys.com \
--to=jbrindle@tresys.com \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.