From: Joe Perches <joe@perches.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
thomas.petazzoni@bootlin.com, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net: mvneta: Fix a typo
Date: Mon, 13 Apr 2020 00:15:53 -0700 [thread overview]
Message-ID: <f1033e80969fce39d9cc97fb924f7d68e5f96f74.camel@perches.com> (raw)
In-Reply-To: <eea1b700-4559-c8d1-1960-1858ed3d90ef@wanadoo.fr>
On Mon, 2020-04-13 at 08:56 +0200, Christophe JAILLET wrote:
> Le 12/04/2020 à 23:35, Joe Perches a écrit :
> > On Sun, 2020-04-12 at 23:20 +0200, Christophe JAILLET wrote:
> > > s/mvmeta/mvneta/
> > nice. how did you find this?
>
> Hi,
>
> This is based on a bash script I've made a while ago (see [1])
> I've slightly updated it, but the idea is still the same. I search
> strings in a file with some variation on the file name (2 inverted
> chars, 1 missing char or 1 modified char).
>
> The output is horrible, and a lot of filtering should be done.
> It is much like noise, with MANY false positives. But I manage to dig
> some interesting stuff out of it.
>
> If interested in the updated script, just ask, but except the concept
> itself, I'm not sure than anything else worth anything and is should be
> rewritten from scratch.
>
> The update includes some tweaks in order to search into Kconfig files
> instead.
>
> CJ
>
> [1]: https://marc.info/?l=kernel-janitors&m=156382201306781&w=4
Nice.
I was wondering if you used levenshtein distance or something else.
https://en.wikipedia.org/wiki/Levenshtein_distance
next prev parent reply other threads:[~2020-04-13 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 21:20 [PATCH] net: mvneta: Fix a typo Christophe JAILLET
2020-04-12 21:35 ` Joe Perches
2020-04-13 6:56 ` Christophe JAILLET
2020-04-13 7:15 ` Joe Perches [this message]
2020-04-13 7:53 ` Christophe JAILLET
2020-04-13 4:21 ` David Miller
2020-04-13 4:22 ` David Miller
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=f1033e80969fce39d9cc97fb924f7d68e5f96f74.camel@perches.com \
--to=joe@perches.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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