From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, abner.chang@hpe.com
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Nickle Wang <nickle.wang@hpe.com>,
"Leif Lindholm (Nuvia address)" <leif@nuviainc.com>
Subject: Re: [edk2-devel] [RedfishPkg PATCH v6 3/4] .azurepipelines/templates: Add RedfishPkg to target build
Date: Wed, 7 Oct 2020 12:54:40 +0200 [thread overview]
Message-ID: <dc2f3749-1ca0-e35e-5316-3dba4a082b56@redhat.com> (raw)
In-Reply-To: <20201007021545.25936-4-abner.chang@hpe.com>
On 10/07/20 04:15, Abner Chang wrote:
> Signed-off-by: Abner Chang <abner.chang@hpe.com>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Nickle Wang <nickle.wang@hpe.com>
> Reviewed-by: Bret Barkelew <Bret.Barkelew@microsoft.com>
> ---
> .azurepipelines/templates/pr-gate-build-job.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.azurepipelines/templates/pr-gate-build-job.yml b/.azurepipelines/templates/pr-gate-build-job.yml
> index 2683687a1c..89c632c0a7 100644
> --- a/.azurepipelines/templates/pr-gate-build-job.yml
> +++ b/.azurepipelines/templates/pr-gate-build-job.yml
> @@ -31,7 +31,7 @@ jobs:
> Build.Pkgs: 'MdeModulePkg'
> Build.Targets: 'RELEASE,NO-TARGET'
> TARGET_NETWORK:
> - Build.Pkgs: 'NetworkPkg'
> + Build.Pkgs: 'NetworkPkg,RedfishPkg'
> Build.Targets: 'DEBUG,RELEASE,NO-TARGET'
> TARGET_OTHER:
> Build.Pkgs: 'PcAtChipsetPkg,ShellPkg'
>
I'd like Sean and/or Bret to re-review this patch, because the related
subthread in the v5 review session seems to have ended with an open
question about NetworkPkg.
https://edk2.groups.io/g/devel/message/65948
http://mid.mail-archive.com/CS1PR8401MB1144EF23CAAF9AF8A147D874FF0A0@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM
It would also be nice to have *some* explanation in the commit message
*why* we're coupling RedfishPkg with NetworkPkg specifically. I'm not
arguing against this coupling by any means, I'd just like to see it
explained.
If someone can propose a concise 1-2 paragraph explanation in response,
I'm happy to reword the commit message myself (including those
paragraphs), when I merge this (v6) series (with Sean's or Bret's
renewed approval of this patch).
Thanks!
Laszlo
next prev parent reply other threads:[~2020-10-07 10:54 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 ` Laszlo Ersek [this message]
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
[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=dc2f3749-1ca0-e35e-5316-3dba4a082b56@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