public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <bret.barkelew@microsoft.com>,
	"'Laszlo Ersek'" <lersek@redhat.com>
Subject: 回复: [EXTERNAL] Re: [edk2-devel] Spell check corrections, package by package
Date: Thu, 28 Jan 2021 09:24:55 +0800	[thread overview]
Message-ID: <00a701d6f514$62ee6530$28cb2f90$@byosoft.com.cn> (raw)
In-Reply-To: <CY4PR21MB01822ABB49BB3D54A4100C7EEFBB9@CY4PR21MB0182.namprd21.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

One BZ is for one package. If few change is made for single module, I would
like to create one combined patch for one package. 

 

Thanks

Liming

发件人: bounce+27952+70825+4905953+8761045@groups.io
<bounce+27952+70825+4905953+8761045@groups.io> 代表 Bret Barkelew via
groups.io
发送时间: 2021年1月27日 18:20
收件人: Laszlo Ersek <lersek@redhat.com>; devel@edk2.groups.io
主题: Re: [EXTERNAL] Re: [edk2-devel] Spell check corrections, package by
package

 

Noted. I’ll see what that looks like. Thanks!

 

- Bret 

 

From: Laszlo Ersek <mailto:lersek@redhat.com> 
Sent: Wednesday, January 27, 2021 1:42 AM
To: devel@edk2.groups.io <mailto:devel@edk2.groups.io> ; Bret Barkelew
<mailto:Bret.Barkelew@microsoft.com> 
Subject: [EXTERNAL] Re: [edk2-devel] Spell check corrections, package by
package

 

On 01/27/21 01:24, brbarkel via groups.io wrote:
> When we added the SpellCheck to CI, we intended to move through package by
package and turn on the PR gate checks (right now they're all in "audit
only"). To do this, we must first fix all the existing spelling errors
and/or update the ignore lists and dictionaries with expected terms.
> 
> I would like to start this process so that we can get enforcement on in
the next couple of months. To pick a random package, I was going to start
with NetworkPkg. Before starting, I wanted to ask what the community would
like to see in terms of the number of patches and/or associated bugs. I'm
comfortable with whatever because I will likely automate the bug opening and
patch association (so beware if you want one bug per fix... there will be a
LOT of bugs).
> 
> Thoughts?

One BZ for OvmfPkg should work, with one associated patch series for
OvmfPkg. Each patch in the OvmfPkg series should fix typos in a given
module (library or driver or application) in OvmfPkg.

Duplicate all of the above for ArmVirtPkg (one BZ, one series, one patch
per module).

Thanks!
Laszlo

 




[-- Attachment #2: Type: text/html, Size: 5648 bytes --]

      reply	other threads:[~2021-01-28  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  0:24 Spell check corrections, package by package brbarkel
2021-01-27  9:42 ` [edk2-devel] " Laszlo Ersek
2021-01-27 10:20   ` [EXTERNAL] " Bret Barkelew
2021-01-28  1:24     ` gaoliming [this message]

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='00a701d6f514$62ee6530$28cb2f90$@byosoft.com.cn' \
    --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