[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1187116082.32555.122.camel@localhost>
Date: Tue, 14 Aug 2007 11:28:02 -0700
From: Joe Perches <joe@...ches.com>
To: Rene Herman <rene.herman@...il.com>
Cc: git@...r.kernel.org, Junio C Hamano <gitster@...ox.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Arjan van de Ven <arjan@...radead.org>,
Trond Myklebust <trond.myklebust@....uio.no>,
Mariusz Kozlowski <m.kozlowski@...land.pl>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch
- scripts/get_maintainer.pl
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
-
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