From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul.moore@hp.com>
Cc: James Morris <jmorris@namei.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, David Howells <dhowells@redhat.com>,
casey@schaufler-ca.com
Subject: Re: linux-next: manual merge of the lblnet tree
Date: Wed, 10 Dec 2008 09:05:44 -0800 [thread overview]
Message-ID: <493FF6E8.2090201@schaufler-ca.com> (raw)
In-Reply-To: <200812081758.10731.paul.moore@hp.com>
Paul Moore wrote:
> On Monday 08 December 2008 4:16:24 pm James Morris wrote:
>
>> On Mon, 8 Dec 2008, Paul Moore wrote:
>>
>>> James, is the security-testing tree rebased regularly or is
>>> suitable to back a tree against?
>>>
>> No, it doesn't get rebased.
>>
>
> Okay, experiment time. I think I managed to pull from all the right
> spots, merge everything appropriately and end up with a security/
> directory that builds so I pushed it back out to the lblnet-2.6_next
> tree. I'm not quite sure the proper etiquette here but I had to fix
> Casey's patch a bit since it would apply cleanly; Casey if you could
> take a look I would appreciate it (it isn't exactly like what Stephen
> posted earlier but it is pretty darn close).
>
>
The Smack Verification Laboratory reports that lblnet-2.6_next is
working as expected for UDP and TCP.
>>> If so, I can rebase the lblnet-2.6_next tree
>>> against security-testing to resolve the conflict ...
>>>
>> Ok, and I can carry your patches in there if necessary.
>>
>
> I would like to figure out to make this work as it is likely to happen
> again at some point in the future, but if I can't get it working
> quickly I may punt on it and ask you to pull in the patches.
>
>
next prev parent reply other threads:[~2008-12-10 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 8:07 linux-next: manual merge of the lblnet tree Stephen Rothwell
2008-12-08 10:46 ` David Howells
2008-12-08 16:09 ` Casey Schaufler
2008-12-08 19:41 ` Paul Moore
2008-12-08 21:16 ` James Morris
2008-12-08 22:58 ` Paul Moore
2008-12-09 4:15 ` Casey Schaufler
2008-12-10 17:05 ` Casey Schaufler [this message]
2008-12-10 17:34 ` Paul Moore
-- strict thread matches above, loose matches on Subject: below --
2008-12-08 7:49 Stephen Rothwell
2008-12-08 19:38 ` Paul Moore
2008-12-08 20:19 ` Jean Delvare
2008-12-09 0:23 ` Stephen Rothwell
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=493FF6E8.2090201@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=sfr@canb.auug.org.au \
/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).