From: Ian Abbott <abbotti@mev.co.uk>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "sclark46@earthlink.net" <sclark46@earthlink.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Ian Abbott <ian.abbott@mev.co.uk>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 00/36] staging: comedi: cb_pcidas: cleanup the driver
Date: Wed, 27 Jun 2012 18:02:34 +0100 [thread overview]
Message-ID: <4FEB3CAA.3060300@mev.co.uk> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0020698F2E703@AUSP01VMBX24.collaborationhost.net>
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).
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2012-06-27 17:02 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 [this message]
2012-06-27 18:51 ` gregkh
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=4FEB3CAA.3060300@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.