[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1284364665.22185.116.camel@Joe-Laptop>
Date: Mon, 13 Sep 2010 00:57:45 -0700
From: Joe Perches <joe@...ches.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Florian Mickler <florian@...kler.org>,
Christoph Hellwig <hch@...radead.org>,
Stephen Hemminger <shemminger@...tta.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Wolfram Sang <w.sang@...gutronix.de>
Subject: Re: [PATCH] get_maintainer.pl: append reason for cc to the name by
default
On Mon, 2010-09-13 at 00:16 -0700, Eric W. Biederman wrote:
> It is trivial for a human to look at a git log and see which changes
> were just global cleanups and which changes were actual maintenance.
> Apparently get_maintainers doesn't have that ability.
Do you have a useful, trivial or non-trivial algorithm
to suggest or is that soft commenting? All I'll say is
AI can be a surprisingly difficult field.
> Have seen some files with something like 5 years of changes without a
> single commit by a maintainer and the only changes happening to it are
> global cleanup changes.
Then likely there's no actual maintainer for that file.
> If get_maintainers would look at MAINTAINERS and validate or invalidate
> that information by looking at git that would be useful.
Some entries in MAINTAINERS are outdated.
Validating MAINTAINERS entries is probably best done once.
I suggest you try that concept out, see what you get, and
make public the results.
--
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