git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Aug 14, 2007, 18:40 UTC
Message-ID
<alpine.LFD.0.999.0708141131140.30176@woody.linux-foundation.org>
In-Reply-To
<1187116082.32555.122.camel@localhost>
On Tue, 14 Aug 2007, Joe Perches wrote:
Show 8 quoted lines
> 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:
	#!/bin/sh
	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 information).

		Linus
Previous: Rene HermanNext: Joe Perches
Message 5 of 38 in “Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl”
  1. Joe PerchesAug 14, 2007
  2. Rene HermanAug 14, 2007
  3. Joe PerchesAug 14, 2007
  4. Rene HermanAug 14, 2007
  5. Linus TorvaldsAug 14, 2007
  6. Joe PerchesAug 14, 2007
  7. Al ViroAug 14, 2007
  8. Joe PerchesAug 14, 2007
  9. Rene HermanAug 15, 2007
  10. Satyam SharmaAug 15, 2007
  11. Rene HermanAug 15, 2007
  12. Kyle MoffettAug 15, 2007
  13. Rene HermanAug 16, 2007
  14. Rene HermanAug 16, 2007
  15. Salikh ZakirovAug 16, 2007
  16. Rene HermanAug 16, 2007
  17. Al ViroAug 16, 2007
  18. Rene HermanAug 16, 2007
  19. Junio C HamanoAug 16, 2007
  20. Rene HermanAug 17, 2007
  21. Krzysztof HalasaAug 15, 2007
  22. Al ViroAug 15, 2007
  23. Richard KnutssonAug 15, 2007
  24. Stefan RichterAug 15, 2007
  25. Ray LeeAug 15, 2007
  26. Joe PerchesAug 16, 2007
  27. Junio C HamanoAug 15, 2007
  28. Joe PerchesAug 15, 2007
  29. Junio C HamanoAug 15, 2007
  30. Rene HermanAug 15, 2007
  31. Stefan RichterAug 15, 2007
  32. Rene HermanAug 15, 2007
  33. Joe PerchesAug 15, 2007
  34. Joe PerchesAug 17, 2007
  35. Joe PerchesAug 17, 2007
  36. - git-send-email.perlJoe Perches, Aug 17, 2007
  37. Junio C HamanoAug 17, 2007
  38. Joe PerchesAug 18, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.