linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	David Howells <dhowells@redhat.com>,
	linux-next@vger.kernel.org
Subject: Re: userns tree ready
Date: Tue, 25 Nov 2008 08:24:06 -0600	[thread overview]
Message-ID: <20081125142406.GA9761@us.ibm.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0811251204450.18891@tundra.namei.org>

Quoting James Morris (jmorris@namei.org):
> On Mon, 24 Nov 2008, Serge E. Hallyn wrote:
> 
> > Hi Stephen,
> > 
> > I've created a new userns tree - although the patches are completely
> > unchanged from before they were pulled along with David's patches.
> > They apply fine either right after James' security-next tree or at
> > the end of linux-next.  The tree is at
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/userns-2.6#next
> > 
> > like before, and is based on James's security-next tree.
> 
> I can merge this into my tree, although if it breaks, I'll need help from 
> you to fix it.

Thanks, James.  I don't know which (security-next or linux-next) is more
appropriate, but I think Stephen may have already added it to
Next/Trees.  I'll of course fix any breakages in any case.

thanks,
-serge

  reply	other threads:[~2008-11-25 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  0:16 userns tree ready Serge E. Hallyn
2008-11-25  0:58 ` Stephen Rothwell
2008-11-25  1:05 ` James Morris
2008-11-25 14:24   ` Serge E. Hallyn [this message]
2008-11-26  6:21     ` James Morris
2008-11-26  6:55       ` 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=20081125142406.GA9761@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.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).