All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masanari Iida <standby24x7@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kees Cook <keescook@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@canonical.com>,
	linux-doc <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2] checkpatch: look for common misspellings
Date: Fri, 12 Sep 2014 19:30:13 +0900	[thread overview]
Message-ID: <CALLJCT36JzRDkkTSqddSDJJPWrMGRhTUhOSd=pcJCAAX4sCBRQ@mail.gmail.com> (raw)
In-Reply-To: <1410497111.9942.26.camel@joe-AO725>

On Fri, Sep 12, 2014 at 1:45 PM, Joe Perches <joe@perches.com> wrote:
> On Fri, 2014-09-12 at 13:09 +0900, Masanari Iida wrote:
>> Test with "reseting" case,  codespell found 21, grep found 26.
>
> Hello Masanari.
>
> How did codespell find any uses of reseting?
> What version of codespell are you using?
> (I tested with 1.7)
>
> Looking at the git tree for codespell,
> https://github.com/lucasdemarchi/codespell.git
> the dictionary there doesn't have reseting.
>
Joe,

First of all, I use codespell 1.4 scripts with my original dictionary
based on 1.4.
So I believe the "reseting" was added by me some times ago.

> If I add reseting->resetting to the dictionary,
> then codespell finds the same 31 uses that
> git grep -i does.
>
My codespell 1.4 works as case sensitive.
That's why we saw a little bit different result.

Masanari

      reply	other threads:[~2014-09-12 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 18:15 [PATCH v2] checkpatch: look for common misspellings Kees Cook
2014-09-08 18:48 ` Joe Perches
2014-09-10  4:37   ` Masanari Iida
2014-09-10  7:00     ` Joe Perches
2014-09-10 22:52 ` Andrew Morton
2014-09-11  2:10   ` Joe Perches
2014-09-11  7:19   ` Geert Uytterhoeven
2014-09-11 14:12     ` Kees Cook
2014-09-11 14:15     ` Joe Perches
2014-09-12  4:09       ` Masanari Iida
2014-09-12  4:45         ` Joe Perches
2014-09-12 10:30           ` Masanari Iida [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='CALLJCT36JzRDkkTSqddSDJJPWrMGRhTUhOSd=pcJCAAX4sCBRQ@mail.gmail.com' \
    --to=standby24x7@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=geert@linux-m68k.org \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.