From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 0/8] Fix invalid interface calls
Date: Thu, 14 Aug 2014 15:45:56 -0400 [thread overview]
Message-ID: <53ED11F4.9040804@tresys.com> (raw)
In-Reply-To: <1407500196-19140-1-git-send-email-sven.vermeulen@siphos.be>
On 8/8/2014 8:16 AM, Sven Vermeulen wrote:
> Found a few inconsistencies in the policy while scripting up some QA.
>
> Sven Vermeulen (8):
> Use logging_search_logs, not logging_search_log
> Use logging_search_logs, not logging_search_log
> Use files_search_etc, not logging_search_etc
> Use files_search_etc, not logging_search_etc
> Use files_search_etc, not files_search_config
> Use corecmd_search_bin, not corecmd_searh_bin
> Use fs_search_tmpfs, not files_search_tmpfs
> Use domain_auto_trans, not auto_trans
>
> ircd.if | 2 +-
> monop.if | 2 +-
> networkmanager.if | 2 +-
> nslcd.if | 2 +-
> rsync.if | 2 +-
> smstools.if | 2 +-
> tgtd.if | 2 +-
> zarafa.if | 2 +-
> 8 files changed, 8 insertions(+), 8 deletions(-)
This set is merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2014-08-14 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 12:16 [refpolicy] [PATCH 0/8] Fix invalid interface calls Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 1/8] Use logging_search_logs, not logging_search_log Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 2/8] " Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 3/8] Use files_search_etc, not logging_search_etc Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 4/8] " Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 5/8] Use files_search_etc, not files_search_config Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 6/8] Use corecmd_search_bin, not corecmd_searh_bin Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 7/8] Use fs_search_tmpfs, not files_search_tmpfs Sven Vermeulen
2014-08-08 12:16 ` [refpolicy] [PATCH 8/8] Use domain_auto_trans, not auto_trans Sven Vermeulen
2014-08-14 19:45 ` Christopher J. PeBenito [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=53ED11F4.9040804@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.