|| ||Linus Torvalds <torvalds-AT-linux-foundation.org>|
|| ||Joe Perches <joe-AT-perches.com>|
|| ||Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch -
|| ||Tue, 14 Aug 2007 11:40:09 -0700 (PDT)|
|| ||Rene Herman <rene.herman-AT-gmail.com>, git-AT-vger.kernel.org,
Junio C Hamano <gitster-AT-pobox.com>,
Alan Cox <alan-AT-lxorguk.ukuu.org.uk>,
Arjan van de Ven <arjan-AT-infradead.org>,
Trond Myklebust <trond.myklebust-AT-fys.uio.no>,
Mariusz Kozlowski <m.kozlowski-AT-tuxland.pl>,
On Tue, 14 Aug 2007, Joe Perches wrote:
> On Tue, 2007-08-14 at 20:03 +0200, Rene Herman wrote:
> > "git info --maintainer drivers/ide/ide-cd.c" or some such would say "Alan
> > Cox <alan@...>".
> Perhaps maintainer(s), approver(s), listener(s)?
> I think something like this should be a git-goal.
> What do the git-wranglers think?
The thing is, if you have git, you can basically already do this.
Do a script like this:
git log --since=6.months.ago -- "$@" |
grep -i '^ [-a-z]*by:.*@' |
sort | uniq -c |
sort -r -n | head
and it gives you a rather good picture of who is involved with a
particular subdirectory or file.
A much *better* picture than some manually maintained thing, in fact,
because it tells you who really does the work, and which way patches go...
(Maybe you want to add a
grep -v '\(Linus Torvalds\)\|\(Andrew Morton\)'
to avoid seeing the normal chain too much, but hey, we probably want to
know too. Anyway - the script can certainly be tweaked, the point is
really just that the git tree _already_ contains the relevant
to post comments)