From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@nuviainc.com" <rebecca@nuviainc.com>,
"gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
"bret.barkelew@microsoft.com" <bret.barkelew@microsoft.com>
Subject: Re: 回复: [edk2-devel] New Year, New PR Thread
Date: Mon, 8 Mar 2021 02:31:12 +0000 [thread overview]
Message-ID: <CO1PR11MB493083526BC3AB654E0967DB8C939@CO1PR11MB4930.namprd11.prod.outlook.com> (raw)
In-Reply-To: <a07704b0-09b2-fcd9-245c-567d8ed6beef@nuviainc.com>
It will be great if PR can replace mail code review.
When can we do the move?
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca
> Cran
> Sent: Monday, March 8, 2021 10:21 AM
> To: devel@edk2.groups.io; gaoliming@byosoft.com.cn;
> bret.barkelew@microsoft.com
> Subject: Re: 回复: [edk2-devel] New Year, New PR Thread
>
> There's a plan to move away from submitting patches as emails, and to
> use pull requests for code review instead.
>
> --
> Rebecca Cran
>
> On 3/7/21 6:20 PM, gaoliming wrote:
> > Bret:
> >
> > What means New Year or New PR Thread?
> >
> > Now, 202102 stable tag has been done. The code can be merged by PR
> > again.
> >
> > Thanks
> >
> > Liming
> >
> > *发件人:*devel@edk2.groups.io <devel@edk2.groups.io> *代表 *Bret
> > Barkelew via groups.io
> > *发送时间:*2021年3月6日1:11
> > *收件人:*devel@edk2.groups.io
> > *主题:*[edk2-devel] New Year, New PR Thread
> >
> > Can we move to PRs yet? Maybe after the stabilization?
> >
> > - Bret
> >
> >
>
>
>
>
>
next prev parent reply other threads:[~2021-03-08 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 17:10 New Year, New PR Thread Bret Barkelew
2021-03-08 1:20 ` 回复: [edk2-devel] " gaoliming
2021-03-08 2:20 ` Rebecca Cran
2021-03-08 2:31 ` Ni, Ray [this message]
2021-03-08 2:43 ` Rebecca Cran
2021-03-08 12:26 ` Ni, Ray
2021-03-08 15:33 ` 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=CO1PR11MB493083526BC3AB654E0967DB8C939@CO1PR11MB4930.namprd11.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