public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Zhichao" <zhichao.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Ni, Ray" <ray.ni@intel.com>, "glin@suse.com" <glin@suse.com>
Cc: "Wu, Hao A" <hao.a.wu@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/PartitionDxe: Revert the child handler blocksize change
Date: Wed, 21 Oct 2020 01:33:01 +0000	[thread overview]
Message-ID: <MWHPR11MB1647CE344C766D6E5078981EF61C0@MWHPR11MB1647.namprd11.prod.outlook.com> (raw)
In-Reply-To: <eff7cc43-e033-37cb-1446-4c19fe9d2822@redhat.com>

Hi Laszlo,

Apologize for the patch merge thing. That is my fault. Base on your comments, I update the commit message with revert info and part of my V1 commit message. And I am thinking there is no other doubt with the reverting. Sometimes the maintainers and reviewers my give the change comment and let the submitter not to send the patch again because the change is tiny. I treat this patch as that condition incorrectly. That's why I contact Ray to review the new commit message and help to push directly if he is OK with it. Sorry for missing you in the process.

Thanks,
Zhichao

> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Tuesday, October 20, 2020 5:53 PM
> To: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>; Gao, Zhichao
> <zhichao.gao@intel.com>; glin@suse.com
> Cc: Wu, Hao A <hao.a.wu@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Tom Lendacky <thomas.lendacky@amd.com>
> Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/PartitionDxe: Revert the child
> handler blocksize change
> 
> Ray,
> 
> On 10/19/20 07:56, Ni, Ray wrote:
> > Zhichao,
> > Can you please update the commit message to address Laszlo's comments?
> 
> why did you merge <https://github.com/tianocore/edk2/pull/1033>?
> 
> PR#1033 was originally submitted as a personal build for Zhichao. When it passed
> CI (and was auto-closed), Zhichao should have posted the updated patch (with
> the cleaned up commit message) as v2 to the mailing list, for the next round of
> review.
> 
> Instead, you reopened the (auto-closed) PR, added the push label, and the
> mergify bot merged the patch. You merged a patch that was not reviewed on the
> list; specifically you didn't give me any chance to re-check the commit message,
> after I pointed out problems with it under the v1 thread. Of course, sometimes
> we (participants in a patch review
> thread) agree that the maintainer will perform some final (small) updates just
> before merging the patch or series, but in this case, that has not happened -- no
> specific wording was proposed or accepted in the thread, as far as I can see.
> 
> Regardin the timeline: as of this writing, Zhichao opened PR#1033 eight hours
> ago, and you made the mergify bot merge the (unreviewed) patch 4 hours ago.
> That is, you just wanted to get rid of it as quickly as possible, without any regard
> to the community (again -- I provided
> *specific* feedback under v1).
> 
> This urgency is especially appalling when contrasted with your and Eric's total
> lack of feedback for Tom Lendacky's patch
> 
>   [edk2-devel] [PATCH v2 1/1]
>   UefiCpuPkg/MpInitLib: Reduce reset vector memory pressure
> 
>   https://edk2.groups.io/g/devel/message/65540
> 
> for almost a *month*. I had to merge that patch yesterday out of desperation
> and embarrassment for your behaviors, with only my R-b added. You forced me
> to break the development process in order not to alienate a prolific contributor.
> All one of you had to do was post an Acked-by.
> 
> You can't make a contributor wait for this long, and you also can't sneak in
> patches without public review (or at least public agreement about the final touch-
> ups). If you can't do maintenance responsibly, for any reason, then *quit*; let
> someone else become maintainer.
> 
> This behavior is a hallmark of the edk2 project not having a healthy open source
> community. Sad.
> 
> Laszlo


  reply	other threads:[~2020-10-21  1:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12  7:22 [PATCH] MdeModulePkg/PartitionDxe: Revert the child handler blocksize change Gao, Zhichao
2020-10-13  2:54 ` Ni, Ray
2020-10-14  5:58   ` [edk2-devel] " Zhiguang Liu
2020-10-15 10:17 ` Laszlo Ersek
2020-10-16  6:42   ` Gary Lin
2020-10-19  2:45     ` Gao, Zhichao
2020-10-19  5:56       ` Ni, Ray
2020-10-19  9:35         ` Gao, Zhichao
2020-10-19 13:12           ` Laszlo Ersek
2020-10-20  1:06             ` Gao, Zhichao
2020-10-20  9:52         ` Laszlo Ersek
2020-10-21  1:33           ` Gao, Zhichao [this message]
2020-10-21 12:26             ` Laszlo Ersek
2020-10-22  5:36               ` Gao, Zhichao
2020-10-19 12:46     ` Laszlo Ersek
2020-10-19  2:41   ` Gao, Zhichao

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=MWHPR11MB1647CE344C766D6E5078981EF61C0@MWHPR11MB1647.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