All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 4/4] scripts/move_maintainer_sections.bash
Date: Mon, 07 Aug 2017 10:04:36 -0700	[thread overview]
Message-ID: <1502125476.2219.28.camel@perches.com> (raw)
In-Reply-To: <c2dd8bc156a1d4c608391c24c4cadf6f866feb2e.1501983685.git.joe@perches.com>

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.

There are some oddities in the results like the
"PCI SUBSYSTEM" block ending up in arch_x86, but for
a first pass I think it's fairly reasonable.

Of course the move_maintainer_sections script isn't
meant to end up in the tree, it was just the easiest
way to send it.

  reply	other threads:[~2017-08-07 17:04 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 [this message]
2017-08-08 18:33     ` Linus Torvalds
2017-08-09  0:37       ` 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=1502125476.2219.28.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.