linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Moore <paul.moore@hp.com>
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: Thu, 28 Feb 2008 02:31:53 +1100	[thread overview]
Message-ID: <20080228023153.50ee6b62.sfr@canb.auug.org.au> (raw)
In-Reply-To: <200802270943.53025.paul.moore@hp.com>

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

Hi Paul,

On Wed, 27 Feb 2008 09:43:52 -0500 Paul Moore <paul.moore@hp.com> wrote:
>
> 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

Added in anticipation, thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-02-27 15:32 UTC|newest]

Thread overview: 21+ 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
2008-02-27 15:31       ` Stephen Rothwell [this message]
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
2024-02-27  6:04 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=20080228023153.50ee6b62.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.moore@hp.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 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).