linux-kernel - Re: [RFC 06/17] ARM: imx: remove custom .init

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: <521346DE.9080600@gmail.com>
Date:	Tue, 20 Aug 2013 12:37:18 +0200
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	Arnd Bergmann <arnd@...db.de>,
	Sascha Hauer <kernel@...gutronix.de>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 06/17] ARM: imx: remove custom .init_time hook

On 08/20/13 12:20, Russell King - ARM Linux wrote:
> On Tue, Aug 20, 2013 at 11:20:06AM +0200, Sebastian Hesselbarth wrote:
>> Yeah, I am having troubles with linux-arm-kernel rejecting my mails
>> because of a suspicious header. I have no clue, what has changed lately
>> with my mails sent by git send-email to make them get stuck.
>
> I believe David feels the same way as I do wrt thread hijacking on
> mailing lists.  The problem is that it seems all too easy for people
> to hit the reply button on some random message from the mailing list,
> change the subject line, and then type an entirely new email into the
> body not related to the message they hit "reply" on.
>
> So, any message which doesn't look like it's a reply to the preceding
> message gets held for moderation.  However, git came along and broke
> that - because every patch sent as a threaded reply to a cover email
> is effectively a "hijack".  Therefore, there's an exception to this -
> if the subject line starts with "[PATCH" then it will be allowed through.
>
> This means if you want to send a RFC, it must be "[PATCH RFC" not just
> "[RFC", because "[RFC" isn't whitelisted.  Maybe it should be, but that
> is David's decision now.

Russell,

I already guessed it has something to do with the In-reply-to line, as
only the patches but not the cover letter gets stuck. Thanks for
pointing me at the missing PATCH prefix and sorry for the noise on
the moderators screen.

For me it is fine not to expand the whitelist and after reading
SubmittingPatches again, it clearly says that RFC is just a tag to be
added after PATCH.

Sebastian

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