From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Fix minor typo in init.if
Date: Mon, 8 Sep 2014 20:27:42 +0200 [thread overview]
Message-ID: <20140908182740.GA24131@x220.network2> (raw)
In-Reply-To: <1410125394-26905-1-git-send-email-nicolas.iooss@m4x.org>
On Sun, Sep 07, 2014 at 11:29:54PM +0200, Nicolas Iooss wrote:
> ---
> policy/modules/system/init.if | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/policy/modules/system/init.if b/policy/modules/system/init.if
> index 921796e547e3..24e62e9c8f03 100644
> --- a/policy/modules/system/init.if
> +++ b/policy/modules/system/init.if
> @@ -814,7 +814,7 @@ interface(`init_rw_initctl',`
> ## </summary>
> ## <param name="domain">
> ## <summary>
> -## Domain allowed access.
> +## Domain to not audit.
> ## </summary>
> ## </param>
> #
> --
> 2.1.0
>
It seems that we have one or more commits that break reference policy since the last release
I am trying to track down the culprits, it started after last release but before or during June 25th
It is going to take time to track this down because build-testing reference policy is so slow.
Looking forward to the day we fully moved to cil/secilc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20140908/89d0eca8/attachment.bin
next prev parent reply other threads:[~2014-09-08 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 21:29 [refpolicy] [PATCH] Fix minor typo in init.if Nicolas Iooss
2014-09-08 18:27 ` Dominick Grift [this message]
2014-09-08 22:46 ` Nicolas Iooss
2014-09-09 12:45 ` Christopher J. PeBenito
2014-09-09 13:28 ` Dominick Grift
2014-09-09 18:40 ` Christopher J. PeBenito
2014-09-09 18:51 ` Dominick Grift
2014-09-10 19:53 ` [refpolicy] Some already-fixed bugs (was: Re: [PATCH] Fix minor typo in init.if) Nicolas Iooss
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=20140908182740.GA24131@x220.network2 \
--to=dac.override@gmail.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.