All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] I have broken out a large section of Fedora policy into the new format.
Date: Mon, 05 Dec 2011 13:55:51 -0500	[thread overview]
Message-ID: <4EDD13B7.9040506@redhat.com> (raw)
In-Reply-To: <4EDCCDC6.40301@tresys.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/05/2011 08:57 AM, Christopher J. PeBenito wrote:
> On 12/01/11 12:11, Daniel J Walsh wrote:
>> I have gotten a lot of fedora contrib policy to compile against
>> the latest refpolicy (base).  Now the question is how do we go
>> about getting the contrib policy merged into refpolicy.
>> 
>> Once we have done a good portion of this, we can start looking
>> at merging in more of the changes between current fedora policy
>> base and refpolicy base.
> 
> You can commit it.  If you're worried about it showing up too soon
> in the base repo, the revision of contrib is pinned in the base
> repo, so it won't show up in the checkouts of the full repo unless
> you go into contrib and pull HEAD.
> 
> Alternatively, we get get an ACK on them before you commit it.
> 
I have no problem checking any of these in, although i would like to
get someone to at least ack the change.  Also some of the patches
included changes to upstream, either missing interfaces or additional
port definitions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7dE7cACgkQrlYvE4MpobNBowCfcQJCitBYrrE3BDdiwD7a8BVq
gb4An3uwynX+sjoDbk/5cj5P1YYT3OeS
=q/Yy
-----END PGP SIGNATURE-----

      reply	other threads:[~2011-12-05 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 17:11 [refpolicy] I have broken out a large section of Fedora policy into the new format Daniel J Walsh
2011-12-05 13:57 ` Christopher J. PeBenito
2011-12-05 18:55   ` Daniel J Walsh [this message]

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=4EDD13B7.9040506@redhat.com \
    --to=dwalsh@redhat.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.