On 10/03/2012 02:53 AM, David Rientjes wrote: > On Tue, 2 Oct 2012, Josh Triplett wrote: > >> This patch series started out as part of another patch series by Daniel >> Santos that makes use of __flatten; I think Daniel plans to have that >> patch series depend on this one. Thus, I think it makes sense to >> introduce __flatten at this point. >> > > Daniel, please introduce __flatten in the patch series that uses it, > thanks. That isn't going to work. I split my patches out into three sets because, otherwise, the list of maintainers that must be CCed exceeds the allowable size of the LKML server and my messages get tagged as spam, causing untold confusion as messages reach maintainers, but not the LKML. Please note from the summary of this patch set (https://lkml.org/lkml/2012/9/28/1136) > This patch set is a dependency of the generic red-black tree patch set, which > I have now split up into three smaller sets. And the patch set this depends upon was submitted 9/28 as well (https://lkml.org/lkml/2012/9/28/1183) and the summary starts with this text: > This patch set depends upon the following: > * Cleanup & new features for compiler*.h and bug.h > * kernel-doc bug fixes (for generating docs) If I move this patch to the other patch set, scripts/get_maintainers.pl will give me a list longer than the LKML administrator will allow for recipients (1024 bytes max) On 09/28/2012 12:46 PM, David Miller wrote: > From: Daniel Santos <danielfsantos@xxxxxxx> > Date: Fri, 28 Sep 2012 09:22:52 -0500 > >> Hello. I'm trying to send a patch set and people in my TO list are >> receiving the emails, but not the LKML. > You can't have email fields larger than 1024 characters, that CC: > list is way too large. There is never any legitimate reason to > CC: so many people, and we block such long email fields since > %99.99999 they indicate spam. If you have any other reasonable suggestions, please post them. Thanks, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
