From: Joe Perches <joe@perches.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Rene Herman <rene.herman@gmail.com>,
git@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Arjan van de Ven <arjan@infradead.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
Date: Tue, 14 Aug 2007 19:12:05 -0700 [thread overview]
Message-ID: <1187143925.32555.208.camel@localhost> (raw)
In-Reply-To: <7vwsvx8twx.fsf@assigned-by-dhcp.cox.net>
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
next prev parent reply other threads:[~2007-08-15 2:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1186984174.10249.7.camel@localhost>
[not found] ` <200708131933.10125.m.kozlowski@tuxland.pl>
[not found] ` <1187026955.2688.4.camel@laptopd505.fenrus.org>
[not found] ` <1187037445.6628.98.camel@heimdal.trondhjem.org>
[not found] ` <1187054366.2757.0.camel@laptopd505.fenrus.org>
[not found] ` <46C10AA8.3090505@gmail.com>
[not found] ` <20070814102033.604c8695@the-village.bc.nu>
[not found] ` <46C1CFFE.4000001@gmail.com>
2007-08-14 17:00 ` [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl Joe Perches
2007-08-14 18:03 ` Rene Herman
2007-08-14 18:28 ` Joe Perches
2007-08-14 18:33 ` Rene Herman
2007-08-14 18:40 ` Linus Torvalds
2007-08-14 18:54 ` Joe Perches
2007-08-14 19:33 ` Al Viro
2007-08-14 19:57 ` Joe Perches
2007-08-15 1:19 ` Rene Herman
2007-08-15 13:33 ` Satyam Sharma
2007-08-15 13:39 ` Rene Herman
2007-08-15 13:52 ` Kyle Moffett
2007-08-16 10:58 ` Rene Herman
2007-08-16 11:08 ` Rene Herman
2007-08-16 11:26 ` Salikh Zakirov
2007-08-16 11:57 ` Rene Herman
2007-08-16 15:40 ` Al Viro
2007-08-16 15:53 ` Rene Herman
2007-08-16 19:00 ` Junio C Hamano
2007-08-17 4:24 ` Rene Herman
2007-08-15 19:37 ` Krzysztof Halasa
2007-08-15 23:19 ` Al Viro
2007-08-15 1:35 ` Richard Knutsson
2007-08-15 9:29 ` Stefan Richter
2007-08-15 15:31 ` Ray Lee
2007-08-16 20:36 ` Joe Perches
2007-08-15 1:31 ` Junio C Hamano
2007-08-15 2:12 ` Joe Perches [this message]
2007-08-15 5:25 ` Junio C Hamano
2007-08-15 5:42 ` Rene Herman
2007-08-15 9:39 ` Stefan Richter
2007-08-15 11:44 ` Rene Herman
2007-08-15 17:26 ` Joe Perches
2007-08-17 2:13 ` Joe Perches
2007-08-17 2:30 ` Joe Perches
2007-08-17 17:54 ` [PATCH] - git-send-email.perl Joe Perches
2007-08-17 23:38 ` Junio C Hamano
2007-08-18 1:51 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1187143925.32555.208.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=rene.herman@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).