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

From: Rene Herman <rene.herman@gmail.com>
Date: Aug 15, 2007, 05:42 UTC
Message-ID: <46C2922D.8000408@gmail.com>
In-Reply-To: <7vlkcdjrmu.fsf@assigned-by-dhcp.cox.net>

On 08/15/2007 07:25 AM, Junio C Hamano wrote:

> Joe Perches <joe@perches.com> writes:

Show 13 quoted lines

>> Rene Herman had an idea about using some git
>> metadata that might be useful.  The completely
>> external data approach suggested by Al Viro 
>> might be OK too in that it wouldn't tie listeners
>> to git requiring more content in git metadata.
> 
> The reason I found Linus's suggestion desirable is because it
> fundamentally does not require git to track any metadata.  If
> the commits are in git, then his script would let you gather the
> data, but otherwise you should be able to do the same by
> grepping patches.  Obviously you would need to filter by paths,
> looking at the diffstat, but the approach does _not_ tie users
> to git.

I believe that wouldn't be much of a problem really. Users in this context are people submitting patches and most people who do will, could and maybe even should be running git these days -- git is very good, GPLd and the Linux source code managament system.

But for occasional contributors that don't, a MAINTAINERS file much like the current could also be generated into releases; it's just that the source would live as file/directory metadata inside git.

Still like the notion of a generic file/directory metadata implementation inside git, through that "<tag>=<value>" system that I suggested. Wouldn't be intrinsically tied to Linux or anything, with any project being free to invent their own tags and has heaps of possible uses, from the current MAINTAINERS info, through summary information, author/licese information, anything goes...

Rene.