From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
SE Linux <selinux@tycho.nsa.gov>,
"Christopher J. PeBenito" <cpebenito@tresys.com>
Subject: Re: I have spit out my current diffs in policy on fedoraproject.org
Date: Fri, 1 Feb 2008 11:07:29 -0500 [thread overview]
Message-ID: <200802011107.29538.paul.moore@hp.com> (raw)
In-Reply-To: <1201878327.4568.158.camel@moss-spartans.epoch.ncsc.mil>
On Friday 01 February 2008 10:05:27 am Stephen Smalley wrote:
> On Fri, 2008-02-01 at 10:01 -0500, Daniel J Walsh wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > http://people.fedoraproject.org/~dwalsh/Policy/
> >
> > Patch is now up to 28000 lines.
> >
> > {snip}
> >
> > Going forward this is going to get more difficult. I think we need
> > more people with the ability to update the reference policy. Even
> > if they just cherry pick through the differences in my patches and
> > upstream. I don't believe one person can keep up with the volume
> > of changes.
>
> Maybe create a fedora branch of refpolicy?
Does this actually solve the problem, or just move the patch problem
from outside refpolicy SVN into a branch within refpolicy? The changes
still need to get merged into the trunk and I'm not sure a branch helps
that any (maybe it does, I guess it all depends on how Chris works).
--
paul moore
linux security @ hp
--
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:[~2008-02-01 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 15:01 I have spit out my current diffs in policy on fedoraproject.org Daniel J Walsh
2008-02-01 15:05 ` Stephen Smalley
2008-02-01 16:07 ` Paul Moore [this message]
2008-02-01 19:39 ` Christopher J. PeBenito
2008-02-01 21:08 ` Daniel J Walsh
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=200802011107.29538.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.