From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 4/4] scripts/move_maintainer_sections.bash
Date: Tue, 08 Aug 2017 17:37:50 -0700 [thread overview]
Message-ID: <1502239070.2219.40.camel@perches.com> (raw)
In-Reply-To: <CA+55aFyQUeLTMLpEwsJBWNgyXCCQRPJqvbORXY1swNzK+2uTdA@mail.gmail.com>
On Tue, 2017-08-08 at 11:33 -0700, Linus Torvalds wrote:
> On Mon, Aug 7, 2017 at 10:04 AM, Joe Perches <joe@perches.com> wrote:
> > On Sat, 2017-08-05 at 18:45 -0700, Joe Perches wrote:
> > > Move MAINTAINERS into a separate directory and reorder it.
> > > Separate various blocks of MAINTAINER sections into separate files.
> >
> > Hey Linus.
> >
> > If/when you try this out, do please let me know what
> > you think.
>
> Ok, I've applied the preparatory patches, but not run the script.
>
> Or rather, I ran the script to see what happens, but I'm not going to
> push the end result.
>
> From a quick look at the end result, I note:
>
> - the arch maintainer split is pointless. It ends up being just one
> entry per architecture
I think that's just preliminary.
Many of the arches have a single maintainer and many
of the drivers specific to that arch could/should be
moved into the arch_<foo> file.
But that doesn't seem easily scriptable.
> for x86_64 not even that (because the x86> pattern matched all of
> them)
What x86_64 section is that? There isn't an arch/x86_64
directory and only 1 combined entry for x86 and x86_64.
> - the two arch maintainer lists that end up being bigger is x86 and
> arm, but the x86 one picked up a log of misleading ones (not just PCI:
> EFI, various random other things too)
Yeah, it's imperfect. Suggestions welcomed.
> - they all end up having the empty line at the top because of how the
> parse-maintainers.pl script works.
That's because I was a bit lazy about the output.
awk '{ if (NR > 1) { print; } }'
would fix it.
Also a 00-README type file for the introductory section
could be useful.
> But *some* of it looks really nice.
>
> The other thing I note is that the way the patches look, this is going
> to be a disaster to merge with any other work - and there really tends
> to be a lot of things touching MAINTAINERS.
It is going to be messy.
Once done it should be easier though.
Even today there's a merge conflict (kinda) with -next and
the alphabetic
reordering movement as one of the sections
is duplicated again. (SYNC
FILE FRAMEWORK)
Collecting the remainder MAINTAINERS patches after an -rc1
and applying them with a quilt like merge might help too
if Andrew feels up to it.
> I'll have to think about it.
>
> But at least the infrastructure patches are applied,
Thanks.
prev parent reply other threads:[~2017-08-09 0:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 1:45 [PATCH 0/4] Scripted update of the MAINTAINERS files Joe Perches
2017-08-06 1:45 ` [PATCH 1/4] parse-maintainers: Add section pattern sorting Joe Perches
2017-08-06 1:45 ` [PATCH 2/4] parse-maintainers: Use perl hash references and specific filenames Joe Perches
2017-08-06 1:45 ` [PATCH 3/4] parse-maintainers: Move matching sections from MAINTAINERS Joe Perches
2017-08-06 1:45 ` [PATCH 4/4] scripts/move_maintainer_sections.bash Joe Perches
2017-08-07 17:04 ` Joe Perches
2017-08-08 18:33 ` Linus Torvalds
2017-08-09 0:37 ` Joe Perches [this message]
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=1502239070.2219.40.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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