From: Darrel Goeddel <dgoeddel@TrustedCS.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: "'SELinux List'" <SELinux@tycho.nsa.gov>,
Karl MacMillan <kmacmillan@mentalrootkit.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Christopher PeBenito <cpebenito@tresys.com>
Subject: Re: [PATCH 2/3 v2] semantic MLS representation for range_trans_rules
Date: Thu, 31 Aug 2006 09:35:17 -0500 [thread overview]
Message-ID: <44F6F3A5.2020401@trustedcs.com> (raw)
In-Reply-To: <1157033407.24429.94.camel@twoface.columbia.tresys.com>
Joshua Brindle wrote:
<snip>
>>diff --exclude=.svn -ruNp selinux-list/checkpolicy/policy_parse.y selinux-rangetrans-2/checkpolicy/policy_parse.y
>>--- selinux-list/checkpolicy/policy_parse.y 2006-08-25 06:16:11.000000000 -0500
>>+++ selinux-rangetrans-2/checkpolicy/policy_parse.y 2006-08-30 06:23:54.000000000 -0500
>>@@ -3616,6 +3616,65 @@ parse_categories(char *id, level_datum_t
>> return 0;
>> }
>>
>>+static int
>>+parse_semantic_categories(char *id, level_datum_t * levdatum,
>
>
> hrm, did lindent do this?
Nope, the cut-paste-modify of parse_categories did it.
--
Darrel
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-08-31 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 16:26 [PATCH 2/3] semantic MLS representation for range_trans_rules Darrel Goeddel
2006-08-29 19:36 ` Karl MacMillan
2006-08-30 14:14 ` Darrel Goeddel
2006-08-29 19:37 ` Joshua Brindle
2006-08-30 14:06 ` Darrel Goeddel
2006-08-31 13:42 ` [PATCH 2/3 v2] " Darrel Goeddel
2006-08-31 14:10 ` Joshua Brindle
2006-08-31 14:35 ` Darrel Goeddel [this message]
2006-09-01 20:12 ` Stephen Smalley
2006-09-01 20:26 ` Stephen Smalley
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=44F6F3A5.2020401@trustedcs.com \
--to=dgoeddel@trustedcs.com \
--cc=SELinux@tycho.nsa.gov \
--cc=cpebenito@tresys.com \
--cc=jbrindle@tresys.com \
--cc=kmacmillan@mentalrootkit.com \
--cc=sds@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.