[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120627185159.GA23014@kroah.com>
Date: Wed, 27 Jun 2012 11:51:59 -0700
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: Ian Abbott <abbotti@....co.uk>
Cc: H Hartley Sweeten <hartleys@...ionengravers.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"sclark46@...thlink.net" <sclark46@...thlink.net>,
Ian Abbott <ian.abbott@....co.uk>,
"fmhess@...rs.sourceforge.net" <fmhess@...rs.sourceforge.net>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/36] staging: comedi: cb_pcidas: cleanup the driver
On Wed, Jun 27, 2012 at 06:02:34PM +0100, Ian Abbott wrote:
> On 2012-06-27 17:45, H Hartley Sweeten wrote:
> >On Wednesday, June 27, 2012 9:31 AM, Stephen Clark wrote:
> >>I there some reason you can't post these as response to this message,
> >>like GKH does, so if readers aren't
> >>interested they can mark the thread read without stepping thru each patch.
> >
> >The only reason is, I'm not sure how to do that... ;-)
> >
> >Greg, any pointers on how?
>
> The easiest way is to use the --compose option of git send-email,
> which lets you edit an introductory email to the patch series you
> are posting and uses that email's ID as the --in-reply-to for all
> the following patch emails (assuming you don't have --chain-reply-to
> set).
Yes, that's the easiest way to do this, and is what I recommend.
greg k-h
--
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