From: Like Xu <like.xu@linux.intel.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Colin Ian King <colin.king@canonical.com>
Subject: Re: [PATCH] scripts/spelling.txt: add more typos to spelling.txt and sort
Date: Fri, 15 Mar 2019 13:45:50 +0800 [thread overview]
Message-ID: <f2a36dc4-fc66-97b9-cadb-ccd37e2b400a@linux.intel.com> (raw)
In-Reply-To: <alpine.LNX.2.21.1903151359480.8@nippy.intranet>
On 2019/3/15 11:07, Finn Thain wrote:
>
> Does it makes sense to list every typo that is simply a transposition of
> characters or a character omitted? This file will become very large very
> quickly if we do that.
We are consistent in one thing: typo hurt eyes.
Those typos are exactly generated from and still existing in the kernel
tree and they're constantly merged out of our carelessness.
> Such errors can be found algorithmically where the correct spelling is
> known. E.g. the file contains 'algorithm' so 'algrthm' can easily be
> obtained programatically.
Nice hint on transposition programmability which means effect to me.
It looks the mistake line could be removed form scripts/spelling.txt
after we add transposition check to scripts/checkpatch.pl. ($0.02)
>
> Suggest you restrict this to common misspellings. That's not a NAK and I'm
> not the relevant maintainer. Just my $0.02.
>
Thanks for your comment.
prev parent reply other threads:[~2019-03-15 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 1:38 [PATCH] scripts/spelling.txt: add more typos to spelling.txt and sort Like Xu
2019-03-15 3:07 ` Finn Thain
2019-03-15 5:45 ` Like Xu [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=f2a36dc4-fc66-97b9-cadb-ccd37e2b400a@linux.intel.com \
--to=like.xu@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=fthain@telegraphics.com.au \
--cc=linux-kernel@vger.kernel.org \
/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