linux-kernel - Re: Large Patch Series in Email

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: <20110715.162210.346975929824395806.davem@davemloft.net>
Date:	Fri, 15 Jul 2011 16:22:10 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mfwitten@...il.com
Cc:	error27@...il.com, kys@...rosoft.com, gregkh@...e.de,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	virtualization@...ts.osdl.org
Subject: Re: Large Patch Series in Email

From: Michael Witten <mfwitten@...il.com>
Date: Fri, 15 Jul 2011 22:55:29 -0000

> On Sat, 16 Jul 2011 00:09:03 +0300, Dan Carpenter wrote:
> 
>> On Fri, Jul 15, 2011 at 06:25:55PM -0000, Michael Witten wrote:
>>>   Do not send more than 15 patches at once to the vger
>>>   mailing lists!!!
>>
>> ... Don't be a whinge bucket.
> 
> Or be respectful of bandwidth, differing email environments, and the
> official guidelines for submitting patches, which I will quote again:
> 
>     If you cannot condense your patch set into a smaller set
>     of patches, then only post say 15 or so at a time and wait
>     for review and integration.
>     ...
>     Do not send more than 15 patches at once to the vger
>     mailing lists!!!

Indeed, it really sucks when people send huge patch sets, do
not do it.

If the official SubmittingPatches document isn't convincing
enough, then maybe me (the vger postmaster) saying it will.
--
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/