On Mon, 2011-01-10 at 20:25 +0100, Uwe Kleine-K?nig wrote: 

Hello Trond,

On Mon, Jan 10, 2011 at 12:20:35PM -0500, Trond Myklebust wrote:

quoted

On Mon, 2011-01-10 at 18:08 +0100, Marc Kleine-Budde wrote: 

quoted

On 01/10/2011 05:25 PM, Trond Myklebust wrote:

quoted

On Mon, 2011-01-10 at 11:50 +0100, Uwe Kleine-K?nig wrote: 

quoted

Hi Trond,

On Sat, Jan 08, 2011 at 06:15:51PM -0500, Trond Myklebust wrote:

quoted

----------------------------------------------------------------------------------- 

It would be great if you could add a "8<" in the line above next time.
Then git-am -c does the right thing (at least I think so).

Sorry. I wasn't aware of that particular idiom. So something like

8<------------------------------------------------------------
From: Trond Myklebust <redacted>
Subject: .....

Yes.

From "man git-mailinfo":
"A line that mainly consists of scissors (either ">8" or "8<") and
perforation (dash "-")"

BTW:
Is this patch a candidate for stable?

Yes. I'm planning on sending it to the stable list after Linus merges it
into mainline.

So there is another idiom for you:  just put

	Cc: stable at kernel.org

in the S-o-b block and Greg will pick it off "automatically".  (Just in
case you don't know, and if you do, maybe someone else learned
something.)

I usually do this, but there is a slight problem with that approach:
Greg gets to do all the work of figuring out to which stable kernels
this particular patch applies. In this case, since we're only talking
about the 2.6.37 kernel, I prefer to use the mailing lists.

Cheers
  Trond
-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust at netapp.com
www.netapp.com