From: "Rebecca Cran" <rebecca@bsdio.com>
To: rfc@edk2.groups.io, bret.barkelew@microsoft.com, "Kinney,
Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>
Subject: Re: [EXTERNAL] Re: [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process
Date: Thu, 14 May 2020 15:46:35 -0600 [thread overview]
Message-ID: <812843fa-36ad-6ef3-42e1-8ec2a3c3e42d@bsdio.com> (raw)
In-Reply-To: <CY4PR21MB0743EB31621F1C92EF34B5F6EFBC0@CY4PR21MB0743.namprd21.prod.outlook.com>
On 5/14/20 3:26 PM, Bret Barkelew via groups.io wrote:
> I feel like this process is a good compromise. It’s not perfect (frankly, I’m a fan of enforced squash merges, which can maintain bisectability if managed well), but it allows for rapid iteration, ease of contribution, and approaches the workflow that many who have never used email to maintain a project would be familiar with.
>
> It’s code management for the Instagram generation, and I for one welcome our new insect overlords.
Or at least, that's what Microsoft is betting on! :D
Personally, I remain unconvinced about the usability of Github Pull
Requests for a project the size of EDK2, but I hope to be proven wrong.
--
Rebecca Cran
next prev parent reply other threads:[~2020-05-14 21:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 2:59 [edk2-rfc] GitHub Pull Request based Code Review Process Michael D Kinney
2020-05-09 4:22 ` Ni, Ray
2020-05-11 17:30 ` Michael D Kinney
2020-05-11 19:47 ` [edk2-devel] " Laszlo Ersek
2020-05-09 18:24 ` Rebecca Cran
2020-05-10 21:29 ` Michael D Kinney
2020-05-10 21:43 ` Rebecca Cran
2020-05-11 1:37 ` Michael D Kinney
2020-05-11 20:05 ` Laszlo Ersek
2020-05-11 20:00 ` Laszlo Ersek
2020-05-11 19:50 ` Laszlo Ersek
2020-05-11 17:27 ` Michael D Kinney
2020-05-11 19:39 ` [edk2-devel] " Laszlo Ersek
2020-05-11 20:09 ` [EXTERNAL] " Bret Barkelew
2020-05-11 20:43 ` Michael D Kinney
2020-05-14 21:26 ` Bret Barkelew
2020-05-14 21:46 ` Rebecca Cran [this message]
2020-05-26 10:08 ` Tomas Pilar (tpilar)
2020-05-15 1:19 ` Michael D Kinney
2020-05-15 4:49 ` Bret Barkelew
2020-05-15 9:07 ` Laszlo Ersek
2020-05-15 15:43 ` Bret Barkelew
2020-05-18 11:48 ` Philippe Mathieu-Daudé
2020-05-15 7:34 ` [EXTERNAL] " Laszlo Ersek
2020-05-15 15:36 ` Bret Barkelew
2020-05-18 2:29 ` Rebecca Cran
2020-05-11 22:07 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2020-05-19 7:21 Nate DeSimone
2020-05-19 16:54 ` Sean
2020-05-19 18:02 ` Nate DeSimone
2020-05-19 19:34 ` Bret Barkelew
2020-05-19 19:59 ` Nate DeSimone
2020-05-19 20:10 ` Bret Barkelew
2020-05-20 21:53 ` Laszlo Ersek
2020-05-22 5:31 ` [EXTERNAL] " Bret Barkelew
2020-05-19 20:41 ` Laszlo Ersek
2020-05-19 22:25 ` Sean
2020-05-21 13:30 ` Laszlo Ersek
2020-05-22 2:59 ` Andrew Fish
2020-05-22 5:48 ` [EXTERNAL] " Bret Barkelew
2020-05-22 17:20 ` Laszlo Ersek
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=812843fa-36ad-6ef3-42e1-8ec2a3c3e42d@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