From: Joe Perches <joe@perches.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: "Duda, Sebastian" <sebastian.duda@fau.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
Wolfgang Mauerer <wolfgang.mauerer@oth-regensburg.de>
Subject: Re: get_maintainers.pl subsystem output
Date: Tue, 23 Jul 2019 06:33:44 -0700 [thread overview]
Message-ID: <269b4b895d64deef4a6d0033dcbed48da11fbce0.camel@perches.com> (raw)
In-Reply-To: <CAKXUXMym7Sd28gVxVXj60XS+aoqM4DAtEp2aA7BUUu06YQYufg@mail.gmail.com>
On Tue, 2019-07-23 at 15:25 +0200, Lukas Bulwahn wrote:
> Hi Joe,
Hi again.
> On Tue, Jul 23, 2019 at 1:18 PM Joe Perches <joe@perches.com> wrote:
> > On Tue, 2019-07-23 at 10:42 +0200, Lukas Bulwahn wrote:
> [...]
> > > Joe, would you support and would you accept if we extend
> > > get_maintainer.pl to provide output of the status in such a way that
> > > the status output can be clearly mapped to the subsystem?
> >
> > Not really, no. I don't see much value in your
> > request to others. It seems you are doing some
> > academic work rather than actually using it for
> > sending patches.
> >
>
> Thank you for that indication. It is good to know that our use case is
> too special to be covered in the existing tool and serves no one else
> besides our research work.
Seems a bit harsh a description, and yes, I've
not ever seen a single request similar to yours
to use get_maintainer in such a manner.
next prev parent reply other threads:[~2019-07-23 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 7:35 get_maintainers.pl subsystem output Duda, Sebastian
2019-07-19 8:50 ` Joe Perches
2019-07-19 9:54 ` Duda, Sebastian
2019-07-19 14:31 ` Joe Perches
2019-07-23 7:29 ` Duda, Sebastian
2019-07-23 8:42 ` Lukas Bulwahn
2019-07-23 11:18 ` Joe Perches
2019-07-23 13:25 ` Lukas Bulwahn
2019-07-23 13:33 ` Joe Perches [this message]
2019-07-23 11:54 ` 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=269b4b895d64deef4a6d0033dcbed48da11fbce0.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=sebastian.duda@fau.de \
--cc=wolfgang.mauerer@oth-regensburg.de \
/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).