From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Refpolicy status
Date: Fri, 29 Apr 2011 09:38:38 -0400 [thread overview]
Message-ID: <4DBABF5E.9060107@tresys.com> (raw)
In-Reply-To: <4DB86A84.9070308@gmail.com>
On 04/27/11 15:12, Dominick Grift wrote:
> On 04/27/2011 08:36 PM, Christopher J. PeBenito wrote:
>> Please let me know if there are particular things that you think should be upstreamed.
>
> Consider synchronizing the cgroup module (also filesystem.fc wrt
> cgroup). You may also want have a look at cobblers policy and its
> dependencies to see if any of it can be merged.
Ok, I already got the filesystem.fc merged in, but its rearranged, so it
looks like a diff between the two trees. I'll look at the cgroup and
cobbler modules.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-04-29 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 18:36 [refpolicy] Refpolicy status Christopher J. PeBenito
2011-04-27 19:12 ` Dominick Grift
2011-04-29 13:38 ` Christopher J. PeBenito [this message]
2011-04-29 13:43 ` Dominick Grift
2011-04-29 13:53 ` Christopher J. PeBenito
2011-04-29 14:31 ` Dominick Grift
2011-04-29 14:36 ` Dominick Grift
2011-04-29 14:56 ` Daniel J Walsh
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=4DBABF5E.9060107@tresys.com \
--to=cpebenito@tresys.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.