From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: 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: Sat, 1 Feb 2020 20:15:06 +0100 [thread overview]
Message-ID: <CAKXUXMyToKuJf_kGXWjP1pu33XbiMD4kpBcqUhJu==-OBQ8TQQ@mail.gmail.com> (raw)
In-Reply-To: <08d88848280f93c171e4003027644a35740a8e8e.camel@perches.com>
On Sat, Feb 1, 2020 at 7:43 PM Joe Perches <joe@perches.com> wrote:
>
> Perhaps this is a defect in the small script as
> get_maintainer does already show the directory and
> files as being maintained.
>
> ie: get_maintainer.pl does this:
>
> ##if pattern is a directory and it lacks a trailing slash, add one
> if ((-d $value)) {
> $value =~ s@([^/])$@$1/@;
> }
>
True. My script did not implement that logic; I will add that to my
script as well.
Fortunately, that is not the major case of issues I have found and
they might need some improvements.
Lukas
next prev parent reply other threads:[~2020-02-01 19:15 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 [this message]
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
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='CAKXUXMyToKuJf_kGXWjP1pu33XbiMD4kpBcqUhJu==-OBQ8TQQ@mail.gmail.com' \
--to=lukas.bulwahn@gmail.com \
--cc=arnd@arndb.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).