[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.00.1010181923450.2764@xanadu.home>
Date: Mon, 18 Oct 2010 19:32:48 -0400 (EDT)
From: Nicolas Pitre <nico@...xnic.net>
To: Daniel Walker <dwalker@...o99.com>
Cc: Russell King <rmk@....linux.org.uk>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, lkml <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, 18 Oct 2010, Daniel Walker wrote:
> On Mon, 2010-10-18 at 18:35 -0400, Nicolas Pitre wrote:
>
> > > 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?
>
> I'm subscribes to review code .. Do you read every patch that cross the
> arm list?
No, But I do read every email subject, and most patch messages. Only
those subjects I know for sure I have no interest in I do delete right
away.
And being a human I sometimes screw up and let something I should have
paid attention fall through the cracks. When that happens I simply fix
the issue after the fact and send a patch, and then life goes on.
If you don't want to actually follow the mailing list traffic, you can
at least filter it by flagging those messages that contain a patch which
touches one of those files you do care about.
Nicolas
--
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