[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1187143925.32555.208.camel@localhost>
Date: Tue, 14 Aug 2007 19:12:05 -0700
From: Joe Perches <joe@...ches.com>
To: Junio C Hamano <gitster@...ox.com>
Cc: Rene Herman <rene.herman@...il.com>, git@...r.kernel.org,
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 18:31 -0700, Junio C Hamano wrote:
> On the other hand, git-send-email _is_ all about sending it
> out, and it needs to know who your patch should reach. I
> think it makes sense to have one script that, given a set of
> paths that are affected, gives a list of potentially
> interested people (that is "Finding" part -- and I see there
> are 600+ patches to implement this on the list), and a new
> option to git-send-email to (1) inspect the patch to see what
> paths are affected, and (2) call that "Find" script to figure
> out whom to send it to, and probably asking for confirmation.
Yes please.
The LK MAINTAINERS file is ugly.
Might there be a git portable way to "find"?
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.
Perhaps both via something like:
--external-find "cmd @filelist"
Thanks, 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