From: Chris PeBenito <chpebeni@linux.microsoft.com>
To: selinux-refpolicy@vger.kernel.org
Subject: [refpolicy3 RFC] Drop suffixes?
Date: Fri, 24 Mar 2023 14:10:10 -0400 [thread overview]
Message-ID: <c0e600cf-b724-8fa9-fb9e-be847f807a22@linux.microsoft.com> (raw)
I am considering dropping the suffixes from users, roles, and types.
init_t would become init, user_r would become user, etc.
Thoughts?
--
Chris PeBenito
next reply other threads:[~2023-03-24 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 18:10 Chris PeBenito [this message]
2023-03-24 18:31 ` [refpolicy3 RFC] Drop suffixes? Dominick Grift
2023-03-25 9:15 ` Russell Coker
2023-03-27 12:32 ` Chris PeBenito
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=c0e600cf-b724-8fa9-fb9e-be847f807a22@linux.microsoft.com \
--to=chpebeni@linux.microsoft.com \
--cc=selinux-refpolicy@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).