DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,  ci@dpdk.org
Subject: Re: spell check
Date: Tue, 16 Nov 2021 09:33:38 -0500	[thread overview]
Message-ID: <f7ttugcnpa5.fsf@redhat.com> (raw)
In-Reply-To: <6042854.nMU7bvWPEF@thomas> (Thomas Monjalon's message of "Tue, 16 Nov 2021 14:51:10 +0100")

Thomas Monjalon <thomas@monjalon.net> writes:

> 16/11/2021 14:46, Lincoln Lavoie:
>> Hi Thomas,
>> 
>> This has been disabled in the lab.   I think it should be possible to get
>> to a base state where there aren't errors, it just requires getting past
>> all of the acronyms and other "strange" (to a spell checker's prospective)
>> parts of the documentation, like function names / prototypes, etc.
>
> There will be always new exceptions.
> It looks more worry than benefit.
>
>> Part of the idea behind putting the spell checker scripts, and more
>> importantly the dictionary and exceptions, into the devtools would be to
>> allow the community to manage that list of exceptions, etc.
>
> I'm not sure it's good to add this requirement on contributors.
>
> Anyway that's a topic for techboard meeting.

I'll make sure to ask about it.

>> On Tue, Nov 16, 2021 at 3:54 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>> 
>> > Hi,
>> >
>> > After some thoughts, I think it is not reasonable to check spelling
>> > in the CI, because we will always have false positives.
>> >
>> > Please could we disable "ci/iol-spell-check-testing" to avoid warnings?


      reply	other threads:[~2021-11-16 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16  8:54 Thomas Monjalon
2021-11-16 13:46 ` Lincoln Lavoie
2021-11-16 13:51   ` Thomas Monjalon
2021-11-16 14:33     ` Aaron Conole [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-all 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=f7ttugcnpa5.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).