From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH Y.A. RESEND] MAINTAINERS: fix alpha. ordering
Date: Thu, 27 Jul 2017 20:12:12 -0700 [thread overview]
Message-ID: <1501211532.5368.42.camel@perches.com> (raw)
In-Reply-To: <CA+55aFxqW9_fqjMMNRSDCCTTp-6W9u6zyV18v85eU9=MRDPJgg@mail.gmail.com>
On Thu, 2017-07-27 at 19:43 -0700, Linus Torvalds wrote:
> On Thu, Jul 27, 2017 at 5:30 PM, Joe Perches <joe@perches.com> wrote:
> >
> > Maybe add a reordering of the patterns so that each pattern list
> > is in a specific order too
>
> I don't think this is wrong per se, but I'm not sure I want to get
> into the merge hell any more than we are already.
>
> Maybe when/if that file is actually split up?
Fine by me.
The get_maintainer patch is a prereq to any split-up.
There are a bunch of little niggly patches that
should go in that remove/update bad F: patterns too
one day.
Given the differences between -next and your tree,
I think only Andrew and quilt would do a decent
job of getting individual patches merged.
Unless you want to take them.
I think it's better to centralize the MAINTAINERS
location in <tree>/MAINTAINERS/<files> than spread
them all over the tree given how many subsystems and
maintainerships are also spread around the tree.
But the get_maintainers patch I sent allows both
styles.
next prev parent reply other threads:[~2017-07-28 3:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 20:32 [PATCH Y.A. RESEND] MAINTAINERS: fix alpha. ordering Randy Dunlap
2017-07-22 2:01 ` Linus Torvalds
2017-07-23 19:49 ` Linus Torvalds
2017-07-23 20:00 ` Linus Torvalds
2017-07-23 20:10 ` Joe Perches
2017-07-23 23:14 ` Linus Torvalds
2017-07-24 1:38 ` Joe Perches
2017-07-28 0:30 ` Joe Perches
2017-07-28 2:43 ` Linus Torvalds
2017-07-28 3:12 ` Joe Perches [this message]
2017-07-28 22:30 ` Linus Torvalds
2017-07-29 1:08 ` Joe Perches
2017-07-29 17:46 ` Joe Perches
2017-07-23 20:05 ` 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=1501211532.5368.42.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).