From: Paul Moore <paul.moore@hp.com>
To: Venkat Yekkirala <vyekkirala@TrustedCS.com>, eparis@redhat.com
Cc: James Morris <jmorris@namei.org>,
selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: [PATCH 0/2] [PATCH 0/2] Updated NetLabel/secid-reconciliation bits and a bugfix
Date: Wed, 04 Oct 2006 16:13:08 -0400 [thread overview]
Message-ID: <452415D4.60007@hp.com> (raw)
In-Reply-To: <36282A1733C57546BE392885C0618592015CF969@chaos.tcs.tcs-sec.com>
Venkat Yekkirala wrote:
> [ EXCLUDING netdev ]
>
>>There was a secid patchset posted on Thursday (9/28) night, I
>>posted the
>>a patch on Friday (9/29) to provide NetLabel support.
>>
>>There was a secid patchset posted on Sunday (10/1) night, I respun the
>>NetLabel support patch on Monday (10/2) - "v2".
>>
>>I respun the NetLabel support patch to take into account Stephen
>>Smalley's comments on Monday (10/2) - "v3".
>>
>>There was a small update to the secid patches yesterday (10/3) so I
>>respun the NetLabel support patch (10/4) - "v4".
>
> You are making my head spin :)
>
Glad it's not just mine ;)
>>>>Venkat, can you please merge the latest my latest NetLabel
>>>>secid support
>>>>patch in with your next release?
>>>
>>>I would, but it currently is premature. As James says, let's
>>>get policy done, the design proven, and tested and then we will
>>>go to netdev with one patchset.
>>
>>I think it's easier to decide on policy, review the design,
>>and test it
>>all if there is one place/patchset with all of the latest
>>bits/patches.
>> Right not it's not that easy with different patches scattered around.
>
> I believe Eric Paris is already keeping track of this and I believe
> people are testing HIS kernel.
Yep, that's what I'm using.
> Actually since your patches need to be modified based on mine, it seems
> to make sense for either you or Eric take on the responsibility of tracking
> the patches and forwarding them on finally.
Why does this seem like a game of hot potato?
:)
If Eric doesn't want to marshall this around I'll take care of it.
--
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:[~2006-10-04 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 19:48 [PATCH 0/2] [PATCH 0/2] Updated NetLabel/secid-reconciliation bits and a bugfix Venkat Yekkirala
2006-10-04 20:13 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 19:11 Venkat Yekkirala
2006-10-04 19:11 ` Venkat Yekkirala
2006-10-04 19:42 ` Paul Moore
2006-10-04 19:42 ` Paul Moore
2006-10-04 15:46 paul.moore
2006-10-04 15:46 ` paul.moore
2006-10-04 18:44 ` James Morris
2006-10-04 18:44 ` James Morris
2006-10-04 18:54 ` Paul Moore
2006-10-04 18:54 ` Paul Moore
2006-10-04 22:56 ` James Morris
2006-10-04 22:56 ` James Morris
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=452415D4.60007@hp.com \
--to=paul.moore@hp.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.com \
/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.