From: brbarkel@microsoft.com
To: devel@edk2.groups.io
Subject: Spell check corrections, package by package
Date: Tue, 26 Jan 2021 16:24:23 -0800 [thread overview]
Message-ID: <s2hz.1611707063465419035.8Afs@groups.io> (raw)
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
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?
[-- Attachment #2: Type: text/html, Size: 782 bytes --]
next reply other threads:[~2021-01-27 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 0:24 brbarkel [this message]
2021-01-27 9:42 ` [edk2-devel] Spell check corrections, package by package Laszlo Ersek
2021-01-27 10:20 ` [EXTERNAL] " 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=s2hz.1611707063465419035.8Afs@groups.io \
--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