public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wang, Jian J" <jian.j.wang@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"leif@nuviainc.com" <leif@nuviainc.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	Andrew Fish <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Remove invalid email address and a few other role changes
Date: Mon, 20 Jul 2020 15:18:39 +0000	[thread overview]
Message-ID: <BYAPR11MB3303DB39C765B4BDA9C3B565B67B0@BYAPR11MB3303.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200720133706.GN12303@vanye>

Leif,


> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Leif
> Lindholm
> Sent: Monday, July 20, 2020 9:37 PM
> To: Wang, Jian J <jian.j.wang@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>; devel@edk2.groups.io; Yao, Jiewen
> <jiewen.yao@intel.com>; Andrew Fish <afish@apple.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Remove invalid email address
> and a few other role changes
> 
> On Mon, Jul 20, 2020 at 04:58:05 +0000, Wang, Jian J wrote:
> > Lief,
> >
> >
> > > -----Original Message-----
> > > From: Leif Lindholm <leif@nuviainc.com>
> > > Sent: Friday, July 17, 2020 5:50 PM
> > > To: Wang, Jian J <jian.j.wang@intel.com>
> > > Cc: Laszlo Ersek <lersek@redhat.com>; devel@edk2.groups.io; Yao, Jiewen
> > > <jiewen.yao@intel.com>; Andrew Fish <afish@apple.com>; Kinney, Michael
> D
> > > <michael.d.kinney@intel.com>
> > > Subject: Re: [PATCH] Maintainers.txt: Remove invalid email address and a
> few
> > > other role changes
> > >
> > > On Fri, Jul 17, 2020 at 07:41:40 +0000, Wang, Jian J wrote:
> > > > > >  SecurityPkg: Secure boot related modules
> > > > > >  F: SecurityPkg/Library/DxeImageVerificationLib/
> > > > > > @@ -480,8 +480,7 @@ M: Zhichao Gao <zhichao.gao@intel.com>
> > > > > >  SignedCapsulePkg
> > > > > >  F: SignedCapsulePkg/
> > > > > >  W:
> > > https://github.com/tianocore/tianocore.github.io/wiki/SignedCapsulePkg
> > > > > > -M: Jiewen Yao <jiewen.yao@intel.com>
> > > > > > -M: Chao Zhang <chao.b.zhang@intel.com>
> > > > > > +M: Jian J Wang <jian.j.wang@intel.com>
> > > > > >
> > > > > >  SourceLevelDebugPkg
> > > > > >  F: SourceLevelDebugPkg/
> > > > > >
> > > > >
> > > > > If Chao still has access to his @intel.com email address (just working
> > > > > in a different role), then it would be nice if he could send an ACK.
> > > > >
> > > > > (The commit message says Chao has left the community, which I
> understand
> > > > > to be the upstream edk2 project; so in theory his Intel email address
> > > > > could still function. On the other hand, the subject line says the email
> > > > > address is now "invalid", so I can't really tell.)
> > > >
> > > > Sorry I brought confusions to you. Actually he left both Intel and
> community
> > > > so the email address is not valid any more. I don' t have his new address
> and
> > > > cannot notify him in this mailing list. But I did get his ACK through WeChat.
> > >
> > > OK. This is not a very unusual situation.
> > >
> > > However, given that, can we break out Chao from this patch and merge
> > > it separately, stating those reasons. If the commit message says so,
> > > the patch is sent by an Intel employee and we can have a reviewed-by
> > > from another Intel employee (like we did for Supreeth for uefi-sct), I
> > > think that would make the history very clear.
> > >
> >
> > I already pushed the patch before noticing your comment. Sorry for it.
> > I'm not sure I get your point. Do you mean I could send the patch in the
> > name of Chao but R-B by me or others? Or I should have separated one
> > maintainer change from other changes in different patches?
> 
> Some of the changes were trivial and just moving people around. Does
> not require steward review.
> 
> The removal of Chao without possibility for them to give an R-b is a
> special case and needs some form of due diligence to verify that the
> right thing is happening. A reviewed-by from a steward is one way to
> do so. It would have made sense to keep it separate.
> 

Understood now. Thanks for the explanations.

Regards,
Jian

> Regards,
> 
> Leif
> 
> >
> > Regards,
> > Jian
> >
> > > Regards,
> > >
> > > Leif
> > >
> > >
> > > > Regards,
> > > > Jian
> > > > >
> > > > >
> > > > > Acked-by: Laszlo Ersek <lersek@redhat.com>
> > > > >
> > > > > Thanks
> > > > > Laszlo
> > > >
> 
> 


  reply	other threads:[~2020-07-20 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  9:31 [PATCH] Maintainers.txt: Remove invalid email address and a few other role changes Wang, Jian J
2020-07-16  9:39 ` [edk2-devel] " Liming Gao
2020-07-16 10:15 ` Yao, Jiewen
2020-07-16 12:34 ` Laszlo Ersek
2020-07-17  7:41   ` Wang, Jian J
2020-07-17  9:49     ` Leif Lindholm
2020-07-20  4:58       ` Wang, Jian J
2020-07-20 13:37         ` Leif Lindholm
2020-07-20 15:18           ` Wang, Jian J [this message]
     [not found]       ` <16235D21A4D28320.6175@groups.io>
2020-07-20  5:00         ` [edk2-devel] " Wang, Jian J

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=BYAPR11MB3303DB39C765B4BDA9C3B565B67B0@BYAPR11MB3303.namprd11.prod.outlook.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