[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150104014119.GE25819@t400>
Date: Sun, 4 Jan 2015 02:41:19 +0100
From: Konrad Zapalowicz <bergo.torino@...il.com>
To: Paul Bolle <pebolle@...cali.nl>
Cc: Greg KH <gregkh@...uxfoundation.org>, devel@...verdev.osuosl.org,
pankaj.saraf@...tech.in, linux-kernel@...r.kernel.org,
abbotti@....co.uk, jitendra kumar khasdev <jkhasdev@...il.com>
Subject: Re: [PATCH 0/5] *** SUBJECT HERE ***
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@...uxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
--
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