[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1287440826.5588.83.camel@c-dwalke-linux.qualcomm.com>
Date: Mon, 18 Oct 2010 15:27:06 -0700
From: Daniel Walker <dwalker@...o99.com>
To: Russell King <rmk@....linux.org.uk>
Cc: Nicolas Pitre <nico@...xnic.net>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Jeremy Kerr <jeremy.kerr@...onical.com>,
Jeff Ohlstein <johlstei@...eaurora.org>
Subject: Re: linux-next: manual merge of the msm tree with the arm tree
On Mon, 2010-10-18 at 22:58 +0100, Russell King wrote:
> On Mon, Oct 18, 2010 at 02:29:22PM -0700, Daniel Walker wrote:
> > That's why we have get_maintainer.pl, it adds in all the CC's
> > automatically ..
>
> $ git diff-tree -u 861bd81ee62a0d6759144c22909a8a3938951656 | scripts/get_maintainer.pl |wc
> 209 624 8021
>
> 209 recipients / 8K of To:/CC: is reasonable?
The answer is not "The tool doesn't work like I want, so screw it." If
the tool doesn't work like we want, then we need to fix the tool not
just walk away. Not to mention that the people involved in making these
patches should still be CC'ing people even if this tool is just helping
them out instead of actually doing it for them.
What it's showing you is anyone that's ever modified those files.. You
just need the people who maintain the files.
how about this,
git show 08a610d9ef5394525b0328da0162d7b58c982cc4 | ./scripts/get_maintainer.pl | wc
58 163 2169
That's the patch we're actually discussing too. It's about one CC per
file modified.
Daniel
--
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/
Powered by blists - more mailing lists