From: "Zeng, Star" <star.zeng@intel.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [Patch] Edk2: Update FmpDevicePkg Maintainers
Date: Wed, 28 Nov 2018 00:53:54 +0000 [thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB048310401F5ADB@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <526f7899-711c-f61f-12a3-800b562c9144@redhat.com>
Philippe,
Good suggestion. :)
Let me send the patch.
Thanks,
Star
-----Original Message-----
From: Philippe Mathieu-Daudé [mailto:philmd@redhat.com]
Sent: Tuesday, November 27, 2018 11:17 PM
To: Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
Cc: Zeng, Star <star.zeng@intel.com>
Subject: Re: [edk2] [Patch] Edk2: Update FmpDevicePkg Maintainers
Hi,
On 27/11/18 15:59, Liming Gao wrote:
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
The usual workflow to hand over is the previous maintainer send the patch, and you Ack-by it.
Exceptions are acceptable but require an explanation in the commit message.
Regards,
Phil.
> ---
> Maintainers.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Maintainers.txt b/Maintainers.txt index
> 9a36f0232b..91a4657adc 100644
> --- a/Maintainers.txt
> +++ b/Maintainers.txt
> @@ -133,7 +133,7 @@ T: git -
> https://github.com/tianocore/edk2-FatPkg.git
>
> FmpDevicePkg
> W: https://github.com/tianocore/tianocore.github.io/wiki/FmpDevicePkg
> -M: Star Zeng <star.zeng@intel.com>
> +M: Liming Gao <liming.gao@intel.com>
> M: Michael D Kinney <michael.d.kinney@intel.com>
>
> IntelFrameworkModulePkg
>
prev parent reply other threads:[~2018-11-28 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 14:59 [Patch] Edk2: Update FmpDevicePkg Maintainers Liming Gao
2018-11-27 15:17 ` Philippe Mathieu-Daudé
2018-11-28 0:53 ` Zeng, Star [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=0C09AFA07DD0434D9E2A0C6AEB048310401F5ADB@shsmsx102.ccr.corp.intel.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