From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: H Hartley Sweeten <hartleys@visionengravers.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"sclark46@earthlink.net" <sclark46@earthlink.net>,
Ian Abbott <ian.abbott@mev.co.uk>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/36] staging: comedi: cb_pcidas: cleanup the driver
Date: Wed, 27 Jun 2012 11:51:59 -0700 [thread overview]
Message-ID: <20120627185159.GA23014@kroah.com> (raw)
In-Reply-To: <4FEB3CAA.3060300@mev.co.uk>
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
prev parent reply other threads:[~2012-06-27 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 0:45 [PATCH 00/36] staging: comedi: cb_pcidas: cleanup the driver H Hartley Sweeten
2012-06-27 16:31 ` Stephen Clark
2012-06-27 16:45 ` H Hartley Sweeten
2012-06-27 17:02 ` Ian Abbott
2012-06-27 18:51 ` gregkh [this message]
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=20120627185159.GA23014@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=hartleys@visionengravers.com \
--cc=ian.abbott@mev.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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