From: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>, Steve Wahl <steve.wahl@hpe.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>
Subject: Re: [PATCH] MAINTAINERS: Add entry for HPE Superdome Flex (UV) maintainers
Date: Fri, 21 Aug 2020 10:05:16 -0700 [thread overview]
Message-ID: <8213206d4764375f32cbea36ea214573248094dc.camel@perches.com> (raw)
In-Reply-To: <CAL_JsqLBfwXamvCB0C9ujhy-BS6P4BpU-MWPuZX+_+sYPVsUSg@mail.gmail.com>
On Fri, 2020-08-21 at 10:45 -0600, Rob Herring wrote:
> +Joe Perches
>
> On Fri, Aug 21, 2020 at 9:48 AM Steve Wahl <steve.wahl@hpe.com> wrote:
> >
> > Signed-off-by: Steve Wahl <steve.wahl@hpe.com>
>
> get_maintainers.pl doesn't work on MAINTAINERS. You need to send this
> to the maintainers of the files listed in the entry below. Looks like
> that would be the x86 maintainers.
>
>
> What did Mauro, David and I do to become MAINTAINERS maintainers?
>
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> (commit_signer:127/806=16%,authored:80/806=10%)
> Rob Herring <robh@kernel.org> (commit_signer:103/806=13%)
> "David S. Miller" <davem@davemloft.net> (commit_signer:99/806=12%)
> linux-kernel@vger.kernel.org (open list)
>
>
> Can we make --no-git-fallback the default? It's useful for
> informational purposes, but never for who to email patches to. Having
> no output would be better, then submitters have to think about where
> to send patches.
Doubtful that improves things. At least the --git-fallback option
shows who modified or got patches accepted to files that are
nominally unmaintained. It also shows the upstream path for those
files via Signed-off-by: lines so I think --git-fallback is generally
a good mechanism and control flag for directly unmaintained files.
> What ever happened to splitting up MAINTAINERS to subdirectories? That
> would help routing MAINTAINERS changes to the right maintainers.
Splitting MAINTAINERS into subdirectories would do nothing
to route patches. It would just be convenience to reduce
the total number of changes to a single file.
Those large number of changes to the single MAINTAINERS file
very rarely have any conflicts either, so it wouldn't really
change the overall number of changes to MAINTAINERS entries
spread around the tree.
You are be welcome to try to split the file and get Linus to
accept it. I gave it a go. Try yourself.
https://lore.kernel.org/patchwork/patch/817857/
next prev parent reply other threads:[~2020-08-21 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 15:48 Steve Wahl
2020-08-21 16:45 ` Rob Herring
2020-08-21 17:05 ` Joe Perches [this message]
2020-08-21 18:17 ` Rob Herring
2020-08-21 18:35 ` Joe Perches
2020-08-21 17:40 ` [PATCH] get_maintainer: Exclude MAINTAINERS file(s) from --git-fallback and --git-blame Joe Perches
2020-08-21 18:05 ` [PATCH V2] get_maintainer: Exclude MAINTAINERS file(s) from --git-fallback Joe Perches
2020-08-24 14:45 ` [PATCH] MAINTAINERS: Add entry for HPE Superdome Flex (UV) maintainers Steve Wahl
2020-08-24 15:36 ` Borislav Petkov
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=8213206d4764375f32cbea36ea214573248094dc.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=dimitri.sivanich@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh@kernel.org \
--cc=russ.anderson@hpe.com \
--cc=steve.wahl@hpe.com \
/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®