From: Joe Perches <joe@perches.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Jan Engelhardt <jengelh@computergmbh.de>,
Sverre Rabbelier <alturin@gmail.com>,
git@vger.kernel.org
Subject: Re: whomto.pl -- finding out whom to send patches to
Date: Thu, 29 May 2008 11:20:33 -0700 [thread overview]
Message-ID: <1212085233.27103.54.camel@localhost> (raw)
In-Reply-To: <20080529210018.GA5508@damson.getinternet.no>
> I've written this perl script that takes a patch as input and prints the
> authors/committers of the affected lines, using git-blame as the back end.
Nice enough script.
It's unfortunate that it can't output the appropriate mailing lists.
I think the shell script that Linus gave awhile ago:
http://lkml.org/lkml/2007/8/14/276
#!/bin/sh
git log --since=6.months.ago -- "$@" |
grep -i '^ [-a-z]*by:.*@' |
sort | uniq -c |
sort -r -n | head
(Maybe you want to add a
grep -v '\(Linus Torvalds\)\|\(Andrew Morton\)'
might work just as well.
I still prefer the file pattern match in MAINTAINERS, or
another external file, and/or data stored directly into GIT
via gitattributes approaches.
This script can give maintainer, mailing lists, and git
contact information for patches or files.
http://lkml.org/lkml/2007/8/20/352
The script works with git-send-email to cc the appropriate parties.
This script and git repository is very old and probably doesn't apply...
git pull git://repo.or.cz/linux-2.6/trivial-mods.git get_maintainer
next prev parent reply other threads:[~2008-05-29 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 21:00 whomto.pl -- finding out whom to send patches to Vegard Nossum
2008-05-29 18:20 ` Joe Perches [this message]
2008-05-29 22:19 ` Jesper Juhl
2008-05-29 23:33 ` Junio C Hamano
2008-05-31 10:33 ` Vegard Nossum
2008-05-30 7:58 ` Andrea Righi
2008-05-31 10:03 ` Vegard Nossum
2008-05-30 9:29 ` Roel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1212085233.27103.54.camel@localhost \
--to=joe@perches.com \
--cc=alturin@gmail.com \
--cc=git@vger.kernel.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).