public inbox for linux-kernel@vger.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: [PATCH 0/4] Scripted update of the MAINTAINERS files
Date: Sat,  5 Aug 2017 18:45:46 -0700	[thread overview]
Message-ID: <cover.1501983685.git.joe@perches.com> (raw)

MAINTAINERS is a very large file.

Update the parse-maintainer script to use specific filenames to
allow scripting of the moving of various bits into separate files.

Add a bash script to move various bits into multiple files.

Joe Perches (4):
  parse-maintainers: Add section pattern sorting
  parse-maintainers: Use perl hash references and specific filenames
  parse-maintainers: Move matching sections from MAINTAINERS
  scripts/move_maintainer_sections.bash

 scripts/move_maintainer_sections.bash | 87 +++++++++++++++++++++++++++++++
 scripts/parse-maintainers.pl          | 97 ++++++++++++++++++++++++++---------
 2 files changed, 161 insertions(+), 23 deletions(-)
 create mode 100755 scripts/move_maintainer_sections.bash

-- 
2.10.0.rc2.1.g053435c

             reply	other threads:[~2017-08-06  1:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06  1:45 Joe Perches [this message]
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

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=cover.1501983685.git.joe@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