From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: re: commit 23cb8490c0d3 ("MAINTAINERS: fix bad file pattern")
Date: Sun, 29 Mar 2020 19:35:22 -0700 [thread overview]
Message-ID: <f53fdf2283e1c847a4c44ea7bea4cb6600c06991.camel@perches.com> (raw)
MAINTAINERS: fix bad file pattern
Testing 'parse-maintainers' due to the previous commit shows a bad file
pattern for the "TI VPE/CAL DRIVERS" entry in the MAINTAINERS file.
There's also a lot of mis-ordered entries, but I'm still a bit nervous
about the inevitable and annoying merge problems it would probably cause
to fix them up.
The MAINTAINERS file is one of my least favorite files due to being huge
and centralized, but fixing it is also horribly painful for that reason.
The identical commit was sent at least twice.
Once directly to you.
https://patchwork.kernel.org/patch/11361131/
https://lore.kernel.org/linux-media/20200128145828.74161-1-andriy.shevchenko@linux.intel.com/
About the pain associated to fixing the file:
I think it would be minimally painful to run
$ ./scripts/parse-maintainers.pl --input=MAINTAINERS --output=MAINTAINERS --order
Immediately before an -rc1 is released.
Relatively few of any pending patches to MAINTAINERS
in -next would be impacted and there would be better
consistency in the silly file.
next reply other threads:[~2020-03-30 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 2:35 Joe Perches [this message]
2020-03-30 7:35 ` Andy Shevchenko
2020-03-30 8:55 ` Joe Perches
2020-04-11 16:43 ` Request to sort MAINTAINERS again just before an -rc1 release Joe Perches
2020-04-12 18:08 ` Linus Torvalds
2020-04-12 19:45 ` 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=f53fdf2283e1c847a4c44ea7bea4cb6600c06991.camel@perches.com \
--to=joe@perches.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®