From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-doc <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: Fix most typos
Date: Fri, 19 Jun 2020 12:37:13 -0700 [thread overview]
Message-ID: <369b8060416ad9507ba1cd1160e20bc2f0ea7e5d.camel@perches.com> (raw)
In-Reply-To: <20200619132045.6120f4eb@lwn.net>
On Fri, 2020-06-19 at 13:20 -0600, Jonathan Corbet wrote:
> On Wed, 10 Jun 2020 16:07:32 -0700
> Joe Perches <joe@perches.com> wrote:
>
> > These are the typos found in scripts/spelling.txt for
> > most of the Documentation/ tree.
> >
> > Scripted with:
> >
> > $ cat scripts/spelling.txt | \
> > grep -v -P "^\s*\#" | \
> > while read line ; do \
> > from=$(echo $line | cut -f1 -d'|'); \
> > to=$(echo $line | cut -f3 -d'|'); \
> > echo "from: $from to: $to" ; \
> > git grep -w --name-only $from | \
> > xargs sed -i "s/\b$from\b/$to/" ; \
> > git checkout scripts/spelling.txt ; \
> > done
> >
> > And some removal of inappropriate conversions
> > in Documentation/translations and a few files
> > where the conversions were incorrect.
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
>
> So this fails badly against current docs-next...any chance of a redo?
This patch still works against current -next.
Maybe your tree should be added to -next so
people don't have to search out specific trees.
git git://git.lwn.net/linux.git docs-next
next prev parent reply other threads:[~2020-06-19 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 23:07 Joe Perches
2020-06-10 23:53 ` Randy Dunlap
2020-06-19 19:20 ` Jonathan Corbet
2020-06-19 19:37 ` Joe Perches [this message]
2020-06-19 19:46 ` Jonathan Corbet
2020-06-19 19:50 ` Randy Dunlap
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=369b8060416ad9507ba1cd1160e20bc2f0ea7e5d.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®