From: Joe Perches <joe@perches.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Karsten Keil <isdn@linux-pingi.de>, Arnd Bergmann <arnd@arndb.de>,
isdn4linux@listserv.isdn4linux.de,
netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section
Date: Mon, 03 Feb 2020 21:35:04 -0800 [thread overview]
Message-ID: <7040e0501f1a04cf09195bdccfcfb05df25962ec.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2002040550540.3062@felia>
On Tue, 2020-02-04 at 06:08 +0100, Lukas Bulwahn wrote:
>
> On Mon, 3 Feb 2020, Andy Shevchenko wrote:
>
> > On Mon, Feb 3, 2020 at 1:08 PM Joe Perches <joe@perches.com> wrote:
> > > On Mon, 2020-02-03 at 12:13 +0200, Andy Shevchenko wrote:
> > > > On Sun, Feb 2, 2020 at 10:45 PM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > ...
> >
> > > > I'm not sure it's ready. I think parse-maintainers.pl will change few
> > > > lines here.
> > >
> > > parse-maintainers would change a _lot_ of the MAINTAINERS file
> > > by reordering section letters.
> >
> > I think it's quite easy to find out if it had changed the record in question.
> >
> I checked it and it does change a bit. My patch adds to a list of file
> entries sorted by "relevance" (not alphabetically) two further minor (by
> relevance) entries, i.e., Kconfig and Makefile, to the end of that list.
>
> The other reorderings would have already applied to the original state;
> rather than trying to "fix" this locally for this one patch here, I would
> prefer to understand why the discussion on splitting the MAINTAINERS file,
> summarized at https://lwn.net/Articles/730509/, got stuck and how I can
> contribute to that. If that bigger change would happen, we could
> automatically clean up all the entries when the things are splitted,
> rather than sending reordering patches to the maintainers that then spend
> time on trying to merge that all back together.
Realistically, ISDN is all but dead.
Perhaps it'd be better to change the entries here to:
F: drivers/isdn/
X: drivers/isdn/capi/
next prev parent reply other threads:[~2020-02-04 5:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 12:43 [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section Lukas Bulwahn
2020-02-01 13:13 ` Arnd Bergmann
[not found] ` <CAHp75Veb1fUkKyJ1_q=iXq=aFqtFrGoVMzoCk15CGaqmARUB+w@mail.gmail.com>
2020-02-01 14:46 ` Lukas Bulwahn
2020-02-01 18:32 ` Andy Shevchenko
2020-02-01 18:41 ` Joe Perches
2020-02-01 19:15 ` Lukas Bulwahn
2020-02-01 20:45 ` Joe Perches
2020-02-01 21:29 ` Lukas Bulwahn
2020-02-02 20:43 ` Jakub Kicinski
2020-02-03 10:13 ` Andy Shevchenko
2020-02-03 11:07 ` Joe Perches
2020-02-03 11:17 ` Andy Shevchenko
2020-02-04 5:08 ` Lukas Bulwahn
2020-02-04 5:35 ` Joe Perches [this message]
2020-02-03 17:35 ` Jakub Kicinski
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=7040e0501f1a04cf09195bdccfcfb05df25962ec.camel@perches.com \
--to=joe@perches.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox