[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <269b4b895d64deef4a6d0033dcbed48da11fbce0.camel@perches.com>
Date: Tue, 23 Jul 2019 06:33:44 -0700
From: Joe Perches <joe@...ches.com>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: "Duda, Sebastian" <sebastian.duda@....de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ralf Ramsauer <ralf.ramsauer@...-regensburg.de>,
Wolfgang Mauerer <wolfgang.mauerer@...-regensburg.de>
Subject: Re: get_maintainers.pl subsystem output
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@...ches.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.
Powered by blists - more mailing lists