linux-kernel - Re: use of opaque subject lines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1423164733.32511.8.camel@x220>
Date:	Thu, 05 Feb 2015 20:32:13 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	"Lad, Prabhakar" <prabhakar.csengg@...il.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	OSUOSL Drivers <devel@...verdev.osuosl.org>,
	Andreas Dilger <andreas.dilger@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Oleg Drokin <oleg.drokin@...el.com>, HPDD-discuss@...1.01.org,
	Andreas Ruprecht <rupran@...server.de>
Subject: Re: use of opaque subject lines

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? People are trying to
bot away the kconfig related messages I send out - which I think is a
very good idea - and I'd like to know what level that bot should reach
before people can get out of its way.

(I happen to think that the stuff I currently do is best done with a
human filter applied.)

Thanks,


Paul Bolle

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