From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: Laszlo Ersek <lersek@redhat.com>,
"rfc@edk2.groups.io" <rfc@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [EXTERNAL] Re: [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process
Date: Fri, 15 May 2020 15:36:49 +0000 [thread overview]
Message-ID: <CY4PR21MB07439762576BBCD76E42B120EFBD0@CY4PR21MB0743.namprd21.prod.outlook.com> (raw)
In-Reply-To: <193b34a1-73ef-a8de-4feb-0d7b829650de@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
“… boundless and bare, The lone and level sands stretch far away.”
- Bret
From: Laszlo Ersek<mailto:lersek@redhat.com>
Sent: Friday, May 15, 2020 12:34 AM
To: rfc@edk2.groups.io<mailto:rfc@edk2.groups.io>; Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>; Kinney, Michael D<mailto:michael.d.kinney@intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: [EXTERNAL] Re: [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process
On 05/14/20 23:26, Bret Barkelew via groups.io wrote:
> It’s code management for the Instagram generation
I find this an extremely good characterization!
And, I find the fact soul-destroying.
Laszlo
[-- Attachment #2: Type: text/html, Size: 2540 bytes --]
next prev parent reply other threads:[~2020-05-15 15:38 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
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 [this message]
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=CY4PR21MB07439762576BBCD76E42B120EFBD0@CY4PR21MB0743.namprd21.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