public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Sean Brogan <spbrogan@outlook.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"michael.kubacki@outlook.com" <michael.kubacki@outlook.com>
Cc: Andrew Fish <afish@apple.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	Leif Lindholm <leif@nuviainc.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Ni, Ray" <ray.ni@intel.com>,
	"Sean Brogan" <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v3 0/7] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg
Date: Thu, 30 Apr 2020 01:18:07 +0000	[thread overview]
Message-ID: <BN6PR11MB397292F955E9FCA56B8ACF8480AA0@BN6PR11MB3972.namprd11.prod.outlook.com> (raw)
In-Reply-To: <38d73ec4-ce01-d6a6-c2dd-5e925afa2084@redhat.com>

Laszlo:


Thanks
Liming
> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Thursday, April 30, 2020 2:04 AM
> To: Sean Brogan <spbrogan@outlook.com>; devel@edk2.groups.io; michael.kubacki@outlook.com
> Cc: Andrew Fish <afish@apple.com>; Ard Biesheuvel <ard.biesheuvel@arm.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>;
> Justen, Jordan L <jordan.l.justen@intel.com>; Leif Lindholm <leif@nuviainc.com>; Gao, Liming <liming.gao@intel.com>; Kinney,
> Michael D <michael.d.kinney@intel.com>; Ni, Ray <ray.ni@intel.com>; Sean Brogan <sean.brogan@microsoft.com>
> Subject: Re: [edk2-devel] [PATCH v3 0/7] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg
> 
> On 04/28/20 18:35, Sean Brogan wrote:
> > I think this was my fault.
> >
> > I was under the impression that a patch needed one of developers listed
> > in the (m) or (r) section of maintainers.txt to provide a reviewed-by.
> > My new understanding is an ack from the (m) plus anyone providing a
> > reviewed-by is enough.
> 
> It depends on the maintainer, too.
> 
> Personally I give R-b if I carefully review the patch and am pleased
> with it.
> 
> I give A-b if I review the patch for general sanity, but don't dig into
> the details. I can also give A-b if someone I trust to do a good review
> in the subject technical area provides an R-b, regardless of whether
> they are an "R" or an otherwise un-designated contributor. With "R"
> folks the chance is higher for me to see such an R-b posted in the first
> place, of course.
> 
> I do think an "M" person should provide "at least" an A-b, even if they
> delegate the actual detailed review to someone else.
> 
I don't think there is such requirement to maintainer now. If you think this is required, 
You can give the proposal to add this requirement in Maintainers.txt.

Thanks
Liming
> So yes, I think your understanding "is correct" (meaning, selfishly,
> that it mostly matches mine, anyway :))
> 
> Thanks
> Laszlo


  reply	other threads:[~2020-04-30  1:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 21:31 [PATCH v3 0/7] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg Michael Kubacki
2020-04-28 12:59 ` Laszlo Ersek
2020-04-28 16:35   ` [edk2-devel] " Sean
2020-04-29 18:03     ` Laszlo Ersek
2020-04-30  1:18       ` Liming Gao [this message]
2020-04-30 11:24         ` Laszlo Ersek
2020-04-30 13:40           ` Leif Lindholm
2020-04-28 19:18   ` Michael Kubacki
2020-04-28 22:18 ` Michael Kubacki

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=BN6PR11MB397292F955E9FCA56B8ACF8480AA0@BN6PR11MB3972.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