public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, brbarkel@microsoft.com
Subject: Re: [edk2-devel] Spell check corrections, package by package
Date: Wed, 27 Jan 2021 10:42:00 +0100	[thread overview]
Message-ID: <65208906-9273-cc27-3503-a37dd6d9cb58@redhat.com> (raw)
In-Reply-To: <s2hz.1611707063465419035.8Afs@groups.io>

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


  reply	other threads:[~2021-01-27  9:42 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 ` Laszlo Ersek [this message]
2021-01-27 10:20   ` [EXTERNAL] Re: [edk2-devel] " Bret Barkelew
2021-01-28  1:24     ` 回复: " gaoliming

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=65208906-9273-cc27-3503-a37dd6d9cb58@redhat.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