public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: devel@edk2.groups.io
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Ard Bieshuevel <ard.bieshuevel@linaro.org>,
	Marcin Wojtas <mw@semihalf.com>
Subject: [PATCH edk2-platforms 0/6] Update Maintainers.txt
Date: Wed,  9 Oct 2019 13:00:07 +0100	[thread overview]
Message-ID: <20191009120013.28076-1-leif.lindholm@linaro.org> (raw)

This set does a few things:
- Imports the documentation header from edk2/Maintainers.txt
- Reformats some maintainer entries to get rid of ',' characters
  in the names.
- Adds F: entries for all sections, and a default fallback section
  for those where there is no match.
- Merges the Marvell sections (designed to work with this format)
  into a single area of responsibility.
- Adds sections for those that now ended up having none other than
  the fallback one (mostly ARM platforms).
- Remove Ard from the default section.

I am intentionally not Cc:ing all affected maintainers, since this
is a reformatting exercise. All roles actually affected are Cc:d.

Cc: Ard Bieshuevel <ard.bieshuevel@linaro.org>
Cc: Marcin Wojtas <mw@semihalf.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>

Leif Lindholm (6):
  Maintainers.txt: Update documentation for new format
  Maintainers.txt: drop ',' from maintainer names
  Maintainers.txt: revamp file to machine-readable format
  Maintainers.txt: merge Marvell platforms and silicon sections
  Maintainers.txt: create explicit sections for remaining modules
  Maintainers.txt: drop Ard from default section

 Maintainers.txt | 175 ++++++++++++++++++++++++++++++++++++++----------
 1 file changed, 140 insertions(+), 35 deletions(-)

--
2.20.1


             reply	other threads:[~2019-10-09 12:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 12:00 Leif Lindholm [this message]
2019-10-09 12:00 ` [PATCH edk2-platforms 1/6] Maintainers.txt: Update documentation for new format Leif Lindholm
2019-10-09 12:51   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-09 12:54     ` Leif Lindholm
2019-10-09 12:59       ` Philippe Mathieu-Daudé
2019-10-09 12:00 ` [PATCH edk2-platforms 2/6] Maintainers.txt: drop ',' from maintainer names Leif Lindholm
2019-10-09 12:53   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-09 13:16     ` Leif Lindholm
2019-10-09 13:36       ` Philippe Mathieu-Daudé
2019-10-09 12:00 ` [PATCH edk2-platforms 3/6] Maintainers.txt: revamp file to machine-readable format Leif Lindholm
2019-10-09 12:31   ` Ard Biesheuvel
2019-10-09 12:47     ` Leif Lindholm
2019-10-09 13:48   ` [edk2-devel] " Liming Gao
2019-10-09 14:27     ` Leif Lindholm
2019-10-09 12:00 ` [PATCH edk2-platforms 4/6] Maintainers.txt: merge Marvell platforms and silicon sections Leif Lindholm
2019-10-09 12:56   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-09 13:21   ` Marcin Wojtas
2019-10-09 12:00 ` [PATCH edk2-platforms 5/6] Maintainers.txt: create explicit sections for remaining modules Leif Lindholm
2019-10-09 12:57   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-09 12:00 ` [PATCH edk2-platforms 6/6] Maintainers.txt: drop Ard from default section Leif Lindholm
2019-10-09 12:32 ` [PATCH edk2-platforms 0/6] Update Maintainers.txt Ard Biesheuvel
2019-10-09 12:46   ` Leif Lindholm

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-list 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=20191009120013.28076-1-leif.lindholm@linaro.org \
    --to=devel@edk2.groups.io \
    /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