From: "Laszlo Ersek" <lersek@redhat.com>
To: "Chang, Abner (HPS SW/FW Technologist)" <abner.chang@hpe.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [RedfishPkg PATCH v6 0/4] Inital RedfishPkg
Date: Wed, 7 Oct 2020 17:48:43 +0200 [thread overview]
Message-ID: <46df1b8d-9640-8779-3326-314edf8cec47@redhat.com> (raw)
In-Reply-To: <CS1PR8401MB114440E9706ABEB5F2518FAAFF0A0@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM>
On 10/07/20 13:23, Chang, Abner (HPS SW/FW Technologist) wrote:
> Thanks for that information, I never read through that guidance... and I should.
>
> One question Leif,
> If the patches get the new tag from reviewers, shall I have to send the new version of patches to the mailing list which includes all of reviewer's tag?
No. If the feedback you get purely consists of feedback tags, and
through them, the patch series becomes eligible for merging, then it is
the maintainer's job to apply your series on a local topic branch of
theirs (git-am), pick up the feedback tags (git-rebase + reword on each
patch), and finally push the topic branch to github, open a PR, set the
"push" label, and let the mergify bot merge the series once the CI run
passes.
https://github.com/tianocore/tianocore.github.io/wiki/Laszlo%27s-unkempt-git-guide-for-edk2-contributors-and-maintainers#maint-04
Thanks
Laszlo
next prev parent reply other threads:[~2020-10-07 15:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 2:15 [RedfishPkg PATCH v6 0/4] Inital RedfishPkg Abner Chang
2020-10-07 2:15 ` [RedfishPkg PATCH v6 1/4] RedfishPkg: Initial commit of RedfishPkg Abner Chang
2020-10-07 9:30 ` Leif Lindholm
2020-10-07 16:29 ` Michael D Kinney
2020-10-08 1:44 ` Abner Chang
[not found] ` <163BE1007D20ADD8.22371@groups.io>
2020-10-08 12:58 ` [edk2-devel] " Abner Chang
2020-10-07 2:15 ` [RedfishPkg PATCH v6 2/4] .pytool: Add CI on RedfishPkg Abner Chang
2020-10-07 2:15 ` [RedfishPkg PATCH v6 3/4] .azurepipelines/templates: Add RedfishPkg to target build Abner Chang
2020-10-07 10:54 ` [edk2-devel] " Laszlo Ersek
2020-10-07 2:15 ` [RedfishPkg PATCH v6 4/4] edk2: Add maintainers to RedfishPkg Abner Chang
2020-10-07 16:28 ` [edk2-devel] " Michael D Kinney
2020-10-07 10:49 ` [edk2-devel] [RedfishPkg PATCH v6 0/4] Inital RedfishPkg Laszlo Ersek
2020-10-07 11:23 ` Abner Chang
2020-10-07 15:00 ` Abner Chang
2020-10-07 15:48 ` Laszlo Ersek [this message]
[not found] ` <163B968D94C2410C.25576@groups.io>
2020-10-08 0:59 ` [edk2-devel] [RedfishPkg PATCH v6 3/4] .azurepipelines/templates: Add RedfishPkg to target build Abner Chang
2020-10-08 1:00 ` Sean
2020-10-08 1:08 ` Abner Chang
[not found] ` <163BDF0D4D469E1C.12039@groups.io>
2020-10-08 3:56 ` Abner Chang
2020-10-14 13:30 ` Abner Chang
[not found] ` <163DDF075C4BB2E8.14646@groups.io>
2020-10-15 1:19 ` Abner Chang
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=46df1b8d-9640-8779-3326-314edf8cec47@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