From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: linux-next: manual merge of the msm tree with the arm tree Date: Tue, 19 Oct 2010 15:18:03 +0200 Message-ID: <201010191518.04147.arnd@arndb.de> References: <20101018103540.7bd9c535.sfr@canb.auug.org.au> <1287442418.5376.38.camel@Joe-Laptop> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de ([212.227.126.186]:56364 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933331Ab0JSNRk (ORCPT ); Tue, 19 Oct 2010 09:17:40 -0400 In-Reply-To: <1287442418.5376.38.camel@Joe-Laptop> Sender: linux-next-owner@vger.kernel.org List-ID: To: Joe Perches Cc: Nicolas Pitre , Daniel Walker , Russell King , Stephen Rothwell , linux-next@vger.kernel.org, lkml , Jeremy Kerr , Jeff Ohlstein On Tuesday 19 October 2010, Joe Perches wrote: > This could have been done: > > $ git show 08a610d9ef5394525b0328da0162d7b58c982cc4 | ./scripts/get_maintainer.pl --nogit | wc -l > 35 > > Even then, using 35 CCs is generally silly. > > It might make some sense for a cover letter and a > patch series where the series made tree-wide changes > in multiple directories. Probably not even then: When a single mail header gets too long, you usually land in some spam filter and get hate mail from the list owners. The lkml limit is 1024 characters (this may come from an official RFC, don't know), which is usually less than 35 recipients. Arnd