From: Laszlo Ersek <lersek@redhat.com>
To: Liming Gao <liming.gao@intel.com>, edk2-devel@lists.01.org
Cc: "Leif Lindholm (Linaro address)" <leif.lindholm@linaro.org>,
Andrew Fish <afish@apple.com>,
Michael Kinney <michael.d.kinney@intel.com>
Subject: Re: [Patch v2] Maintainers.txt: Add the rule to hand over the package maintain role
Date: Wed, 28 Nov 2018 20:59:20 +0100 [thread overview]
Message-ID: <b6ad40a5-0dd8-11ae-c6f4-b9ab507b95fe@redhat.com> (raw)
In-Reply-To: <20181128140318.19436-1-liming.gao@intel.com>
On 11/28/18 15:03, Liming Gao wrote:
> In V2, change his to the, and add new maintainers follow up.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> ---
> Maintainers.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Maintainers.txt b/Maintainers.txt
> index 91a4657adc..e102114c34 100644
> --- a/Maintainers.txt
> +++ b/Maintainers.txt
> @@ -6,7 +6,10 @@ EDK II.
>
> In general, you should not privately email the maintainer. You should
> email the edk2-devel list, and Cc the package maintainers and
> -reviewers.
> +reviewers. If the package maintainer wants to hand over the role to
> +other people, the package maintainer should send the patch to update
> +Maintainers.txt with new maintainer, and the new maintainer should
> +follow up with an Acked-by or a Reviewed-by.
>
> Descriptions of section entries:
>
>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
prev parent reply other threads:[~2018-11-28 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 14:03 [Patch v2] Maintainers.txt: Add the rule to hand over the package maintain role Liming Gao
2018-11-28 15:13 ` Philippe Mathieu-Daudé
2018-11-28 20:03 ` Laszlo Ersek
2018-11-29 0:06 ` Gao, Liming
2018-11-28 19:59 ` Laszlo Ersek [this message]
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=b6ad40a5-0dd8-11ae-c6f4-b9ab507b95fe@redhat.com \
--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