From: James Morris <jmorris@namei•org>
To: Paul Moore <paul.moore@hp•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Andrew Morton <akpm@linux-foundation•org>,
linux-next@vger•kernel.org
Subject: Re: Labeled Networking tree for linux-next
Date: Thu, 24 Jul 2008 04:16:27 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0807240415200.14401@us.intercode.com.au> (raw)
In-Reply-To: <200807231244.45084.paul.moore@hp.com>
On Wed, 23 Jul 2008, Paul Moore wrote:
> Hello,
>
> I've created a new labeled networking tree to feed bits into linux-next
> which should replace the lblnet-2.6_testing tree which is currently
> used. The new tree (currently empty) can be found here:
>
> * git://git.infradead.org/users/pcmoore/lblnet-2.6_next
Is this stuff likely to affect more of net/ or security/ ? I think it
should go in via either the networking or security-testing trees.
--
James Morris
<jmorris@namei•org>
next prev parent reply other threads:[~2008-07-23 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:44 Labeled Networking tree for linux-next Paul Moore
2008-07-23 18:16 ` James Morris [this message]
2008-07-23 20:19 ` Paul Moore
2008-07-24 0:06 ` Stephen Rothwell
2008-07-24 2:53 ` David Miller
2008-07-24 13:47 ` Paul Moore
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=Xine.LNX.4.64.0807240415200.14401@us.intercode.com.au \
--to=jmorris@namei$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.moore@hp$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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