From: Chris PeBenito <pebenito@ieee.org>
To: Russell Coker <russell@coker.com.au>, selinux-refpolicy@vger.kernel.org
Subject: Re: obsolete policy
Date: Tue, 16 Feb 2021 09:37:08 -0500 [thread overview]
Message-ID: <979708e2-2cab-37a4-bf17-60ee0a15af1b@ieee.org> (raw)
In-Reply-To: <2087042.fIsVSkRV3x@liv>
On 1/26/21 6:28 AM, Russell Coker wrote:
> Below is the list of policy modules which seem to be obsolete.
>
> For future reference I think we should we make it standard procedure to
> include the upstream URL for software related to a module in any case that
> it's non-obvious. I could have saved at least an hour if there was a list of
> upstream URLs to check.
I think it would be useful, but I also wonder how useful it will be over time
since projects move from time to time to different providers, github, gitlab,
bitbucket, etc.
I'd list this as something that should be there but is not required.
--
Chris PeBenito
next prev parent reply other threads:[~2021-02-16 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 11:28 obsolete policy Russell Coker
2021-01-26 13:29 ` Russell Coker
2021-02-16 14:37 ` Chris PeBenito [this message]
2021-03-05 1:30 ` Russell Coker
2021-03-06 18:54 ` Chris PeBenito
2021-03-06 19:57 ` Sugar, David
[not found] ` <BLAPR15MB37648F5B6947DB93197727DEC2959@BLAPR15MB3764.namprd15.prod.outlook.com>
2021-03-06 23:11 ` Russell Coker
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=979708e2-2cab-37a4-bf17-60ee0a15af1b@ieee.org \
--to=pebenito@ieee.org \
--cc=russell@coker.com.au \
--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 NNTP newsgroup(s).