From: Paul Bolle <pebolle@tiscali.nl>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jitendra kumar khasdev <jkhasdev@gmail.com>,
abbotti@mev.co.uk, hsweeten@visionengravers.com,
devel@driverdev.osuosl.org, pankaj.saraf@nektech.in,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] *** SUBJECT HERE ***
Date: Sat, 03 Jan 2015 23:54:34 +0100 [thread overview]
Message-ID: <1420325674.9624.65.camel@x220> (raw)
In-Reply-To: <20150103164516.GB30268@kroah.com>
On Sat, 2015-01-03 at 08:45 -0800, Greg KH wrote:
> On Sat, Jan 03, 2015 at 02:06:22PM +0530, jitendra kumar khasdev wrote:
> > *** BLURB HERE ***
>
> What blurb? What subject?
jitendra used git-send-email to send this series. You'd expect
git-send-email to die with an error if the cover letter, which it should
see first, still contains these "*** [...] HERE ***" markers. What's the
reason it doesn't do that?
Paul Bolle
next prev parent reply other threads:[~2015-01-03 22:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 8:36 [PATCH 0/5] *** SUBJECT HERE *** jitendra kumar khasdev
2015-01-03 8:36 ` [PATCH 1/5] Staging: comedi: fix line over 80 characters warning jitendra kumar khasdev
2015-01-03 12:20 ` Sudip Mukherjee
2015-01-03 8:36 ` [PATCH 2/5] " jitendra kumar khasdev
2015-01-03 8:36 ` [PATCH 3/5] " jitendra kumar khasdev
2015-01-03 8:36 ` [PATCH 4/5] " jitendra kumar khasdev
2015-01-03 8:36 ` [PATCH 5/5] " jitendra kumar khasdev
2015-01-03 16:45 ` [PATCH 0/5] *** SUBJECT HERE *** Greg KH
2015-01-03 22:54 ` Paul Bolle [this message]
2015-01-04 1:41 ` Konrad Zapalowicz
2015-01-05 22:18 ` Paul Bolle
-- strict thread matches above, loose matches on Subject: below --
2019-03-23 12:53 Cristian Sicilia
2019-03-23 19:24 ` Matt Ranostay
2012-01-26 20:11 Chase Maupin
2012-01-26 20:12 ` Maupin, Chase
2012-01-31 16:22 ` Maupin, Chase
2010-06-14 9:44 Nicholas A. Bellinger
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=1420325674.9624.65.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=jkhasdev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.saraf@nektech.in \
/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.