Re: linux-next: manual merge of the msm tree with the arm tree

[Joe Perches]

On Mon, 2010-10-18 at 18:35 -0400, Nicolas Pitre wrote:
> On Mon, 18 Oct 2010, Daniel Walker wrote:
> > 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?
> > 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.
> What is a mailing list for, then?  Why are you subscribed?
> Please get real or get away.

Too true.  The patch is entirely for arch/arm and
relatively few if any maintainers need to be cc'd.

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.

Even so, lkml will sensibly reject emails with more
than a couple dozen CC's as likely spam.

For cover letters, I generally use:

	./scripts/get_maintainer.pl --nom -l --nogit

and for each patch in a series

	./scripts/get_maintainer.pl --no-git

There is a change in the get_maintainers.pl in Andrew
Morton's mm tree to default to --nogit.

The new get_maintainer.pl is available from:
	git://repo.or.cz/linux-2.6/get_maintainer.git 20100922_gm 
Have a look at:
	http://repo.or.cz/w/linux-2.6/get_maintainer.git


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/