From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: cilc: name space inconsistency
Date: Mon, 20 Oct 2014 15:34:35 +0200 [thread overview]
Message-ID: <20141020133434.GA32063@e145.network2> (raw)
In-Reply-To: <20141017131548.GA1524@e145.network2>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
On Fri, Oct 17, 2014 at 03:15:49PM +0200, Dominick Grift wrote:
> I started rewriting my policy using name spaces again. I was assuming the the name space issues were fixed.
>
> However I am encountering, what i believe, is an inconsistency.
Never mind, its just a warning. I build with -v and sometimes i forget that and get alarmed by any char it returns
[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]
prev parent reply other threads:[~2014-10-20 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 13:15 cilc: name space inconsistency Dominick Grift
2014-10-20 13:34 ` Dominick Grift [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=20141020133434.GA32063@e145.network2 \
--to=dac.override@gmail.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.