From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
"Marvin Häuser" <mhaeuser@posteo.de>
Subject: Re: [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label
Date: Thu, 16 Mar 2023 13:59:49 -0600 [thread overview]
Message-ID: <d6fda6cc-6f79-43e8-ddec-0311593a8468@bsdio.com> (raw)
In-Reply-To: <CO1PR11MB49290B996E9F4AD2EB0F3AD3D2BF9@CO1PR11MB4929.namprd11.prod.outlook.com>
Is this still a requirement since Laszlo's departure from the project?
I seem to recall it was him who made it a sticking point of moving to a
GitHub PR workflow originally with the requirement to have emails of
everything.
--
Rebecca Cran
On 3/15/23 4:34 PM, Michael D Kinney wrote:
>
> Hi Marvin,
>
> One of the long standing requirements for tianocore is to have a
> history of all patch series and all
>
> code review activity archived in the mailing list.
>
> Adopting the full PR workflow right now for even a portion of
> edk2-platforms would have a gap in the
>
> history of patch series and review comments.
>
> edk2-staging repo branches can choose to use this style if they want,
> but when content is migrated from
>
> edk2-staging into main repos, we want the email archive for that activity.
>
> Mike
>
> *From:*Marvin Häuser <mhaeuser@posteo.de>
> *Sent:* Wednesday, March 15, 2023 3:24 PM
> *To:* Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
> *Subject:* Re: [edk2-devel] [edk2-platforms] Enable GitHub PR,
> protected branches, and 'push' label
>
> Hi Mike,
>
> Could this be extended to allow for a full PR workflow, if the package
> maintainers would prefer so? We would like to utilise this for
> Ext4Pkg. It could be considered a trial. :)
>
> Best regards,
> Marvin
>
> _._,_._,_
> ------------------------------------------------------------------------
>
next prev parent reply other threads:[~2023-03-16 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 20:02 [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label Michael D Kinney
2023-03-15 22:24 ` [edk2-devel] " Marvin Häuser
2023-03-15 22:34 ` Michael D Kinney
2023-03-16 19:54 ` Marvin Häuser
2023-03-16 19:59 ` Rebecca Cran [this message]
2023-03-17 9:33 ` Gerd Hoffmann
2023-03-17 10:36 ` Rebecca Cran
2023-03-17 10:48 ` Rebecca Cran
[not found] ` <174D2F2BAAB7643C.10271@groups.io>
2023-03-17 10:57 ` Rebecca Cran
2023-03-17 15:27 ` Michael D Kinney
-- strict thread matches above, loose matches on Subject: below --
2023-03-17 12:32 Marvin Häuser
2023-03-17 12:57 ` Rebecca Cran
2023-03-17 13:44 ` Gerd Hoffmann
2023-03-17 14:08 ` Marvin Häuser
2023-03-17 14:20 ` Rebecca Cran
2023-03-17 15:37 ` Michael D Kinney
2023-03-17 14:22 ` Rebecca Cran
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=d6fda6cc-6f79-43e8-ddec-0311593a8468@bsdio.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