public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Konrad Zapalowicz <bergo.torino@gmail.com>
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: Mon, 05 Jan 2015 23:18:50 +0100	[thread overview]
Message-ID: <1420496330.14308.37.camel@x220> (raw)
In-Reply-To: <20150104014119.GE25819@t400>

On Sun, 2015-01-04 at 02:41 +0100, Konrad Zapalowicz wrote:
> 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 already has to parse the file(s) it's provided with. Perhaps it
already has checks to validate Subject: lines. Would an extra test be a
burden?

> 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.

A warning would be too late: the message with the silly subject would be
already sent out.

> 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.

It's good if people are careful. It's also good if programs help to
avoid silly mistakes.


Paul Bolle


  reply	other threads:[~2015-01-05 22:18 UTC|newest]

Thread overview: 13+ 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
2015-01-05 22:18       ` Paul Bolle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-23 12:53 Cristian Sicilia
2019-03-23 19:24 ` Matt Ranostay

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=1420496330.14308.37.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=abbotti@mev.co.uk \
    --cc=bergo.torino@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox