Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
From: Joe Perches <joe@perches.com>
Date: 2007-08-14 18:28:36
Also in:
lkml
Possibly related (same subject, not in this thread)
- 2007-08-17 · Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl · Rene Herman <hidden>
- 2007-08-17 · Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl · Joe Perches <joe@perches.com>
- 2007-08-17 · Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl · Joe Perches <joe@perches.com>
- 2007-08-16 · Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl · Junio C Hamano <hidden>
- 2007-08-15 · Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl · Al Viro <hidden>
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? Until a time in the future when a system like that exists, I suggest keeping MAINTAINERS up-to-date with F: pattern It'll be useful as git-set-maintainer seeds at least.
sticking headers on every source file isn't nice anyway -- it's meta-information and the SCM can maintain it.
It's like looking at $CVS$ keywords. Unsightly. cheers, Joe