From: Laszlo Ersek <lersek@redhat.com>
To: tye1 <ting.ye@intel.com>
Cc: edk2-devel@lists.01.org, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] Maintainers.txt: Change package maintainer and reviewer of CryptoPkg.
Date: Thu, 13 Dec 2018 11:37:51 +0100 [thread overview]
Message-ID: <f2b6770c-4de7-a2c2-5b4e-205b9034f861@redhat.com> (raw)
In-Reply-To: <20181213074106.10300-1-ting.ye@intel.com>
Hi Ting,
On 12/13/18 08:41, tye1 wrote:
> Cc: Gang Wei <gang.wei@intel.com>
> Cc: Jian Wang <jian.j.wang@intel.com>
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Ting Ye <ting.ye@intel.com>
> ---
> Maintainers.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Maintainers.txt b/Maintainers.txt
> index 001d8ba010..d5cb305da9 100644
> --- a/Maintainers.txt
> +++ b/Maintainers.txt
> @@ -102,8 +102,9 @@ S: Maintained
>
> CryptoPkg
> W: https://github.com/tianocore/tianocore.github.io/wiki/CryptoPkg
> -M: Qin Long <qin.long@intel.com>
> M: Ting Ye <ting.ye@intel.com>
> +R: Gang Wei <gang.wei@intel.com>
> +R: Jian Wang <jian.j.wang@intel.com>
>
> DynamicTablesPkg
> W: https://github.com/tianocore/tianocore.github.io/wiki/DynamicTablesPkg
>
This patch does not conform to the rule that we added lately; please see
commit 9ebef6c0a7d3 ("Maintainers.txt: Add the rule to hand over the
package maintain role", 2018-11-29).
In other words, the patch should be sent out by Qin Long. Even though
you co-maintain CryptoPkg with Qin Long, you shouldn't be able to
deprive Qin Long from the role.
Thanks,
Laszlo
next prev parent reply other threads:[~2018-12-13 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 7:41 [PATCH] Maintainers.txt: Change package maintainer and reviewer of CryptoPkg tye1
2018-12-13 7:59 ` Wang, Jian J
2018-12-13 8:11 ` Wei, Gang
2018-12-13 10:37 ` Laszlo Ersek [this message]
2018-12-13 13:14 ` Gao, Liming
2018-12-13 18:30 ` Long, Qin
2018-12-14 0:47 ` Ye, Ting
2018-12-14 9:38 ` Laszlo Ersek
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=f2b6770c-4de7-a2c2-5b4e-205b9034f861@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