LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: "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 22:53:24 +1100	[thread overview]
Message-ID: <20081026225324.6231397d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <10752.1225019273@redhat.com>

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

Hi David,

On Sun, 26 Oct 2008 11:07:53 +0000 David Howells <dhowells@redhat.com> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > It would be good if you could have a "next" (or "creds-next" or
> > something) branch in your tree and I can fetch that (that way I don't
> > have to keep updating my configs).  It is OK if thet branch rebases and
> > may just be an alias for another branch (or a subset if you have
> > experimental stuff in there.  Remember "posted, reviewed, tested before
> > it is in linux-next".
> 
> 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 :-)

> What base for the patches?  Linus's head?

Yes. Or whatever it is based on now if that merges OK with Linus' head
(try a test merge).  Just don't base on linux-next :-)

What I want is exactly what you will ask/have asked Linus to fetch but
without the branch name changing .. I care more about the name changing
than the contents changing.

So .. what branch do I fetch tomorrow?  (Hint: if you have your version
for Linus checked out then type "git branch next" and reply to this email
saying "next" :-))
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

  reply	other threads:[~2008-10-26 11:53 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 [this message]
2008-10-26 16:04     ` David Howells
2008-10-26 16:11     ` David Howells
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=20081026225324.6231397d.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --cc=jmorris@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.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).