LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
James Morris <jmorris@namei.org>
Subject: Re: linux-next: Tree for Feb 27
Date: Wed, 27 Feb 2008 09:43:52 -0500 [thread overview]
Message-ID: <200802270943.53025.paul.moore@hp.com> (raw)
In-Reply-To: <20080228010626.fd4e00d2.sfr@canb.auug.org.au>
On Wednesday 27 February 2008 9:06:26 am Stephen Rothwell wrote:
> On Tue, 26 Feb 2008 23:00:59 -0800 Andrew Morton
<akpm@linux-foundation.org> wrote:
> > So who's missing now?
> >
> > I have:
>
> Of this list, I *don't* have:
...
> > git-lblnet
I keep the labeled networking patches for the upcoming (in this case
2.6.26) kernel here:
* git://git.infradead.org/users/pcmoore/lblnet-2.6_testing
Patches for the current kernel (in this case 2.6.25) live here:
* git://git.infradead.org/users/pcmoore/lblnet-2.6
Both are currently empty.
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2008-02-27 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 6:03 linux-next: Tree for Feb 27 Stephen Rothwell
2008-02-27 6:09 ` Stephen Rothwell
2008-02-27 7:00 ` Andrew Morton
2008-02-27 14:06 ` Stephen Rothwell
2008-02-27 14:43 ` Paul Moore [this message]
2008-02-27 15:31 ` Stephen Rothwell
2008-02-27 16:06 ` Paul Moore
2008-02-27 17:30 ` Jeff Garzik
2008-02-27 22:54 ` Stephen Rothwell
2008-02-27 19:55 ` Theodore Tso
2008-02-27 23:06 ` Stephen Rothwell
2012-02-27 7:20 Stephen Rothwell
2013-02-27 2:44 Stephen Rothwell
2014-02-27 6:03 Stephen Rothwell
2015-02-27 4:49 Stephen Rothwell
2017-02-27 3:34 Stephen Rothwell
2018-02-27 4:03 Stephen Rothwell
2019-02-27 6:44 Stephen Rothwell
2020-02-27 4:22 Stephen Rothwell
2023-02-27 1:18 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=200802270943.53025.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=akpm@linux-foundation.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).