From: Joe Perches <joe@perches.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust to filesystem doc ReST conversion
Date: Wed, 04 Mar 2020 14:57:04 -0800 [thread overview]
Message-ID: <e43f0cf0117fbfa8fe8c7e62538fd47a24b4657a.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2003042145340.2698@felia>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Wed, 2020-03-04 at 21:50 +0100, Lukas Bulwahn wrote:
>
> On Wed, 4 Mar 2020, Jonathan Corbet wrote:
>
> > On Wed, 4 Mar 2020 08:29:50 +0100
> > Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> > > Jonathan, pick pick this patch for doc-next.
> >
> > Sigh, I need to work a MAINTAINERS check into my workflow...
> >
>
> I getting closer to have zero warnings on the MAINTAINER file matches and
> then, I would set up a bot following the mailing lists to warn when anyone
> sends a patch that potentially introduces such warning.
Hey Lukas.
I wrote a hacky script that sent emails
for invalid MAINTAINER F: and X: patterns
a couple years back.
I ran it in September 2018 and March 2019.
It's attached if you want to play with it.
The email sending bit is commented out.
The script is used like:
$ perl ./scripts/get_maintainer.pl --self-test=patterns | \
cut -f2 -d: | \
while read line ; do \
perl ./dump_section.perl $line \
done
[-- Attachment #2: dump_section.perl --]
[-- Type: application/x-perl, Size: 3558 bytes --]
next prev parent reply other threads:[~2020-03-04 22:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 7:29 [PATCH] MAINTAINERS: adjust to filesystem doc ReST conversion Lukas Bulwahn
2020-03-04 7:59 ` Mauro Carvalho Chehab
2020-03-04 10:54 ` Lukas Bulwahn
2020-03-04 20:10 ` Jonathan Corbet
2020-03-04 20:24 ` Joe Perches
2020-03-04 20:28 ` Mauro Carvalho Chehab
2020-03-04 21:02 ` Lukas Bulwahn
2020-03-04 21:24 ` Joe Perches
2020-03-05 6:14 ` Mauro Carvalho Chehab
2020-03-04 20:50 ` Lukas Bulwahn
2020-03-04 21:01 ` Jonathan Corbet
2020-03-04 22:57 ` Joe Perches [this message]
2020-03-06 21:17 ` Lukas Bulwahn
2020-03-07 10:01 ` Mauro Carvalho Chehab
2020-03-07 15:12 ` Joe Perches
2020-03-08 2:59 ` [PATCH] parse-maintainers: Do not sort section content by default Joe Perches
2020-03-26 16:45 ` Joe Perches
2020-03-26 22:54 ` Linus Torvalds
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=e43f0cf0117fbfa8fe8c7e62538fd47a24b4657a.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab+huawei@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).