[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1378852189.23501.54.camel@dabdike.int.hansenpartnership.com>
Date: Tue, 10 Sep 2013 15:29:49 -0700
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@...com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
LKML-scsi <linux-scsi@...r.kernel.org>
Subject: Re: [PATCH 1/4] hpsa: add HP Smart Array Gen9 PCI ID's
On Tue, 2013-09-10 at 22:17 +0000, Miller, Mike (OS Dev) wrote:
>
> -----Original Message-----
> From: James Bottomley [mailto:James.Bottomley@...senPartnership.com]
> Sent: Tuesday, September 10, 2013 5:02 PM
> To: Miller, Mike (OS Dev)
> Cc: Andrew Morton; LKML; LKML-scsi
> Subject: Re: [PATCH 1/4] hpsa: add HP Smart Array Gen9 PCI ID's
>
> On Wed, 2013-09-04 at 15:05 -0500, Mike Miller wrote:
> > Patch 1 of 4
> >
> > From: Mike Miller <mike.miller@...com>
>
> Just for future reference, doing it this way means I have to edit the patch. The way git am works when applying patches is that if the first body line is a keyword it recognises (like From: or Subject: or Date:) it will fold that into the commit metadata, otherwise everything becomes the commit message. So by putting the redundant "patch 1 of 4" first, git thinks the entire body is the commit message.
>
> James
>
> Sorry about that. I didn't realize git worked that way. So let me ask
> a dumb question, just having [PATCH x/y] in the subject line is
> enough?
Yes, that's what all the apply scripts go by.
> Would you like me to resubmit the patchset?
No; I just edited the messages this time.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists