[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081026225324.6231397d.sfr@canb.auug.org.au>
Date: Sun, 26 Oct 2008 22:53:24 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: David Howells <dhowells@...hat.com>
Cc: "Serge E. Hallyn" <serue@...ibm.com>,
lkml <linux-kernel@...r.kernel.org>, jmorris@...ibm.com
Subject: Re: [PATCH] User namespaces: set of cleanups (v2)
Hi David,
On Sun, 26 Oct 2008 11:07:53 +0000 David Howells <dhowells@...hat.com> wrote:
>
> Stephen Rothwell <sfr@...b.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@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists