From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Valentin Rothberg <valentinrothberg@gmail.com>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
OSUOSL Drivers <devel@driverdev.osuosl.org>,
Andreas Dilger <andreas.dilger@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Oleg Drokin <oleg.drokin@intel.com>,
HPDD-discuss@ml01.01.org, Andreas Ruprecht <rupran@einserver.de>
Subject: Re: use of opaque subject lines
Date: Thu, 05 Feb 2015 12:53:52 -0800 [thread overview]
Message-ID: <1423169632.4752.12.camel@perches.com> (raw)
In-Reply-To: <20150205200639.GA16729@kroah.com>
On Thu, 2015-02-05 at 12:06 -0800, Greg Kroah-Hartman wrote:
> On Thu, Feb 05, 2015 at 08:32:13PM +0100, Paul Bolle wrote:
> > On Thu, 2015-02-05 at 09:57 -0800, Greg Kroah-Hartman wrote:
> > > And _NEVER_ have automated scripts create patches and send them out. I
> > > only know of ONE person/bot that gets away with this, and you are not
> > > that person, sorry. It it not a script on the receiving end of your
> > > output, so don't use a script to create a mess for them to dig through.
> >
> > Mind if I ask which person/bot you have in mind?
>
> If you don't know that there is a bot doing patches, then that proves it
> is so good that people do not realize it :)
Hmm. That proves bots should be used to create patches.
next prev parent reply other threads:[~2015-02-05 20:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 13:36 [PATCH] staging: lustre: osc: Fix sparse warning about osc_init Andreas Ruprecht
2015-02-02 14:16 ` Al Viro
2015-02-02 19:13 ` Andreas Ruprecht
2015-02-05 16:30 ` use of opaque subject lines Al Viro
2015-02-05 16:57 ` Lad, Prabhakar
2015-02-05 17:57 ` Greg Kroah-Hartman
2015-02-05 18:22 ` Lad, Prabhakar
2015-02-05 19:32 ` Paul Bolle
2015-02-05 20:06 ` Greg Kroah-Hartman
2015-02-05 20:53 ` Joe Perches [this message]
2015-02-05 17:08 ` Joe Perches
2015-02-05 17:25 ` Dan Carpenter
2015-02-05 17:31 ` Joe Perches
2015-02-05 17:32 ` Joe Perches
2015-02-05 17:35 ` Dan Carpenter
2015-02-05 18:01 ` Joe Perches
2015-02-05 18:26 ` Dan Carpenter
2015-02-05 18:03 ` Greg Kroah-Hartman
2015-02-02 19:24 ` [PATCH] staging: lustre: osc: Make osc_init() static Andreas Ruprecht
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=1423169632.4752.12.camel@perches.com \
--to=joe@perches.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=pebolle@tiscali.nl \
--cc=prabhakar.csengg@gmail.com \
--cc=rupran@einserver.de \
--cc=valentinrothberg@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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