From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, "Serge E. Hallyn" <serue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
jmorris@us.ibm.com
Subject: Re: [PATCH] User namespaces: set of cleanups (v2)
Date: Sun, 26 Oct 2008 16:11:20 +0000 [thread overview]
Message-ID: <11616.1225037480@redhat.com> (raw)
In-Reply-To: <20081026225324.6231397d.sfr@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Those patches aren't likely to change much, and they get hit with LTP
> > regularly.
>
> They already changed between what I thought was the correct branch and
> what was the correct branch :-)
If you're talking about between James's two creds branches, he did ask you to
pull from the new one - just before you went on holiday, so I suspect you
didn't see it till you got back.
If you're talking about my creds-v3 and creds-v4 branches, the difference was
merge conflicts with Linus, nothing more. And really, I should just have
thrown the merge on top of creds-v3 rather than trying to maintain my patchset
and producing a creds-v4. That's one of the reasons I'd like to recreate my
kernel.org tree - to get rid of the unnecessary labels.
David
next prev parent reply other threads:[~2008-10-26 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 17:48 [PATCH] User namespaces: set of cleanups (v2) Serge E. Hallyn
2008-10-24 18:44 ` David Howells
2008-10-24 19:18 ` Serge E. Hallyn
2008-10-24 19:40 ` David Howells
2008-10-25 2:08 ` Stephen Rothwell
2008-10-26 11:07 ` David Howells
2008-10-26 11:53 ` Stephen Rothwell
2008-10-26 16:04 ` David Howells
2008-10-26 16:11 ` David Howells [this message]
2008-10-25 2:05 ` Stephen Rothwell
2008-10-28 16:21 ` Serge E. Hallyn
2008-10-29 7:36 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-10-20 23:01 Serge E. Hallyn
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=11616.1225037480@redhat.com \
--to=dhowells@redhat.com \
--cc=jmorris@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.