[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46C30220.6060007@gmail.com>
Date: Wed, 15 Aug 2007 15:39:44 +0200
From: Rene Herman <rene.herman@...il.com>
To: Satyam Sharma <satyam@...radead.org>
CC: Al Viro <viro@....linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Joe Perches <joe@...ches.com>, 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>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
On 08/15/2007 03:33 PM, Satyam Sharma wrote:
[ git info --maintainer ]
> I'd really _love_ a tool that does all that what you've proposed above!
>
> But why does it have to be "git-info" or anything in the git(7) suite for
> that matter? This sounds like a job for a different specialised tool,
> along with ".metatags" kind of files dispersed in the source tree.
To automatically move (and delete) the meta-data alongside the files
themselves is a reason.
More generally -- shouldn't it? This is about source management (well, maybe
more about project management, but...) and the source code management tool
looks to be the right place for that. The different parts of git are
somewhat/fairly stand-alone as is, no?
Rene.
-
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