mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andy Whitcroft <apw@canonical.com>,
	Kees Cook <keescook@chromium.org>,
	Masanari Iida <standby24x7@gmail.com>,
	codespell@googlegroups.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: Add optional --codespell dictionary to find more typos
Date: Thu, 05 Mar 2015 11:21:35 -0800	[thread overview]
Message-ID: <1425583295.31859.29.camel@perches.com> (raw)
In-Reply-To: <CAKi4VA+TWa8hdqqnXJgVpeEOxp+n8JbEeBEbRUy31OvmFphfkw@mail.gmail.com>

On Thu, 2015-03-05 at 16:13 -0300, Lucas De Marchi wrote:
> On Thu, Mar 5, 2015 at 3:52 PM, Joe Perches <joe@perches.com> wrote:
> > If a codespell dictionary exists, use it if desired.
> > default is off, maybe it could be turned on later.
> >
> > codespell's dictionary format allows multiple possible corrections,
> > ignore that for now and only use the first suggestion.
> 
> Most of them were particularly added to avoid wrong suggestions in
> kernel code base (admittedly a long time ago)...
> Wouldn't it be better to output the entire list of suggestions as
> codespell the tool does?

If you want to write the code, be my guest.

> I'm not a perl guru, but couldn't we have a single option like
> --codespell / --codespell=FILE ?

Not easily.  There's no easy way to turn off codespell like that.



      reply	other threads:[~2015-03-05 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 18:52 Joe Perches
2015-03-05 19:13 ` Lucas De Marchi
2015-03-05 19:21   ` Joe Perches [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=1425583295.31859.29.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=codespell@googlegroups.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    --cc=standby24x7@gmail.com \
    /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

all inboxes | Powered by JetHome®