All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Zapalowicz <bergo.torino@gmail.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, pankaj.saraf@nektech.in,
	linux-kernel@vger.kernel.org, abbotti@mev.co.uk,
	jitendra kumar khasdev <jkhasdev@gmail.com>
Subject: Re: [PATCH 0/5] *** SUBJECT HERE ***
Date: Sun, 4 Jan 2015 02:41:19 +0100	[thread overview]
Message-ID: <20150104014119.GE25819@t400> (raw)
In-Reply-To: <1420325674.9624.65.camel@x220>

On 01/03, Paul Bolle wrote:
> 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?

git send-email does one thing and one thing only - sends stuff via
email. I do not see why it should parse the emails and decide whether to
complete the operation or break based on what is in the emails. It could
warn though however since the cover letter is a product of different
command introducing this logic would tightly couple those which is not
good.

I guess that it is better that people who send stuff acctually care what
they are sending. I mean that pretty quickly you learn to send the
series of patches first to yourself and review before it goes out to the
public.
 
> 
> Paul Bolle
> 
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2015-01-04  1:41 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
2015-01-04  1:41     ` Konrad Zapalowicz [this message]
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=20150104014119.GE25819@t400 \
    --to=bergo.torino@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkhasdev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.saraf@nektech.in \
    --cc=pebolle@tiscali.nl \
    /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.