From: Russell Coker <russell@coker.com.au>
To: selinux@tycho.nsa.gov
Cc: Chris PeBenito <pebenito@ieee.org>, refpolicy <refpolicy@oss.tresys.com>
Subject: Re: ANN: Reference Policy Release
Date: Wed, 02 Nov 2016 15:13:07 +1100 [thread overview]
Message-ID: <8799489.dRRxGQOAEO@russell.coker.com.au> (raw)
In-Reply-To: <6f8bd54a-758b-01ba-0958-16bd6c5b15ed@ieee.org>
On Sunday, 23 October 2016 5:29:25 PM AEDT Chris PeBenito wrote:
> A new release of the SELinux Reference Policy is now available on the
> GitHub site, https://github.com/TresysTechnology/refpolicy.
https://github.com/TresysTechnology/refpolicy/wiki/DownloadRelease
The archive at the above page has the files policy.28 and policy.30.orig which
comprise more than half the compressed archive size.
Could you make a new release without them? Otherwise we are going to have
that in all the distribution archives and mirror sites.
Also in future could we have more frequent releases? More frequent upstream
releases makes it easier for distribution people to send changes upstream and
gives a greater incentive to do so.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2016-11-02 4:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 21:29 ANN: Reference Policy Release Chris PeBenito
2016-11-02 4:13 ` Russell Coker [this message]
2016-11-02 22:19 ` Chris PeBenito
-- strict thread matches above, loose matches on Subject: below --
2019-02-01 20:22 ANN: Reference Policy release Chris PeBenito
2018-07-01 17:40 Chris PeBenito
2017-02-04 19:02 ANN: Reference Policy Release Chris PeBenito
2015-12-08 15:49 Christopher J. PeBenito
2014-12-03 19:31 Christopher J. PeBenito
2014-03-11 13:33 Christopher J. PeBenito
2013-04-24 20:56 Christopher J. PeBenito
2012-07-26 16:41 Christopher J. PeBenito
2012-02-15 20:19 Christopher J. PeBenito
2011-07-26 18:44 Christopher J. PeBenito
2010-12-14 16:39 Christopher J. PeBenito
2010-05-25 20:02 Christopher J. PeBenito
2009-11-17 15:28 Christopher J. PeBenito
2009-07-30 18:45 Christopher J. PeBenito
2008-12-10 20:24 Christopher J. PeBenito
2008-10-14 18:34 Christopher J. PeBenito
2008-07-02 15:37 Christopher J. PeBenito
2008-04-02 18:14 Christopher J. PeBenito
2007-12-14 18:56 Christopher J. PeBenito
2007-09-28 15:19 Christopher J. PeBenito
2007-10-02 15:29 ` Shintaro Fujiwara
2007-06-29 17:30 Christopher J. PeBenito
2007-04-17 15:07 Christopher J. PeBenito
2007-04-19 20:45 ` Manoj Srivastava
2007-04-19 20:56 ` Karl MacMillan
2007-04-19 23:10 ` Manoj Srivastava
2006-12-12 22:35 Christopher J. PeBenito
2006-10-19 12:57 Christopher J. PeBenito
2006-03-07 15:28 Christopher J. PeBenito
2006-01-17 21:31 Christopher J. PeBenito
2005-12-07 16:40 Christopher J. PeBenito
2005-12-15 22:28 ` Serge E. Hallyn
2005-12-16 17:59 ` Daniel J Walsh
2005-12-18 23:20 ` Serge E. Hallyn
2006-01-03 15:48 ` Christopher J. PeBenito
2005-10-19 21:50 Christopher J. PeBenito
2005-09-22 20:56 Christopher J. PeBenito
2005-09-07 17:22 Christopher J. PeBenito
2005-08-26 15:57 Christopher J. PeBenito
2005-08-02 15:49 Christopher J. 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=8799489.dRRxGQOAEO@russell.coker.com.au \
--to=russell@coker.com.au \
--cc=pebenito@ieee.org \
--cc=refpolicy@oss.tresys.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 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).