From: Joe Perches <joe@perches.com>
To: Laura Abbott <labbott@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jeremy Cline <jcline@redhat.com>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: New project: get_maintainer.pl web app
Date: Fri, 09 Feb 2018 13:21:32 -0800 [thread overview]
Message-ID: <1518211292.14014.34.camel@perches.com> (raw)
In-Reply-To: <8089f485-a0f6-aa5f-ad19-16b69eb07f46@redhat.com>
On Fri, 2018-02-09 at 13:07 -0800, Laura Abbott wrote:
> Hi,
>
> get_maintainers.pl has been the standard script for figuring out where to
> send patches or bug reports. It has the disadvantage of requiring a kernel
> tree to actually run though, which makes it harder for bug reports to
> came in. I've started working on a small project to expose get_maintainers.pl
> as a web app. This would let users enter information from a patch or crash
> and call out to get_maintainers.pl. The current project just lets users
> enter in a file path and it displays the output as is. There's lots of options
> for what we could do with the output (omitting e-mails for those maintainers
> who don't want to participate, printing out more helpful warnings etc.)
>
> The project is at https://pagure.io/get_maintainers and is not even close
> to ready for primetime (passing data to get_maintainer.pl almost certainly
> needs more thought). I'm mostly interested if anyone else would find this
> useful or has general feedback.
Is there a website already setup too?
next prev parent reply other threads:[~2018-02-09 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 21:07 New project: get_maintainer.pl web app Laura Abbott
2018-02-09 21:21 ` Joe Perches [this message]
2018-02-09 21:30 ` Laura Abbott
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=1518211292.14014.34.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=jcline@redhat.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.