From: William Breathitt Gray <william.gray@linaro.org>
To: Joe Perches <joe@perches.com>
Cc: Baoquan He <bhe@redhat.com>, Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>, Slark Xiao <slark_xiao@163.com>,
kafai <kafai@fb.com>, vgoyal <vgoyal@redhat.com>,
dyoung <dyoung@redhat.com>, ast <ast@kernel.org>,
daniel <daniel@iogearbox.net>, andrii <andrii@kernel.org>,
"martin.lau" <martin.lau@linux.dev>, song <song@kernel.org>,
yhs <yhs@fb.com>, "john.fastabend" <john.fastabend@gmail.com>,
kpsingh <kpsingh@kernel.org>, sdf <sdf@google.com>,
haoluo <haoluo@google.com>, jolsa <jolsa@kernel.org>,
dhowells <dhowells@redhat.com>, peterz <peterz@infradead.org>,
mingo <mingo@redhat.com>, will <will@kernel.org>,
longman <longman@redhat.com>, "boqun.feng" <boqun.feng@gmail.com>,
tglx <tglx@linutronix.de>, bigeasy <bigeasy@linutronix.de>,
kexec <kexec@lists.infradead.org>,
linux-doc <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
linux-cachefs <linux-cachefs@redhat.com>
Subject: Re: [PATCH v2] docs: Fix typo in comment
Date: Mon, 25 Jul 2022 09:57:04 -0400 [thread overview]
Message-ID: <Yt6hMD+HIaERgrqg@fedora> (raw)
In-Reply-To: <5bd85a7241e6ccac7fe5647cb9cf7ef22b228943.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
On Mon, Jul 25, 2022 at 06:52:15AM -0700, Joe Perches wrote:
> On Fri, 2022-07-22 at 07:45 +0800, Baoquan He wrote:
> > On 07/21/22 at 11:40am, Randy Dunlap wrote:
> > > On 7/21/22 11:36, Jonathan Corbet wrote:
> > > > "Slark Xiao" <slark_xiao@163.com> writes:
> > > > > May I know the maintainer of one subsystem could merge the changes
> > > > > contains lots of subsystem? I also know this could be filtered by
> > > > > grep and sed command, but that patch would have dozens of maintainers
> > > > > and reviewers.
> > > >
> > > > Certainly I don't think I can merge a patch touching 166 files across
> > > > the tree. This will need to be broken down by subsystem, and you may
> > > > well find that there are some maintainers who don't want to deal with
> > > > this type of minor fix.
> > >
> > > We have also seen cases where "the the" should be replaced by "then the"
> > > or some other pair of words, so some of these changes could fall into
> > > that category.
> >
> > It's possible. I searched in Documentation and went through each place,
> > seems no typo of "then the". Below patch should clean up all the 'the the'
> > typo under Documentation.
> []
> > The fix is done with below command:
> > sed -i "s/the the /the /g" `git grep -l "the the " Documentation`
>
> This command misses entries at EOL:
>
> Documentation/trace/histogram.rst: Here's an example where we use a compound key composed of the the
>
> Perhaps a better conversion would be 's/\bthe the\b/the/g'
It would be good to check for instances that cross newlines as well;
i.e. "the" at the end of a line followed by "the" at the start of the
next line. However, this would require some thought to properly account
for comment blocks ("*") and other similar prefixes that should be
ignored.
William Breathitt Gray
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-07-25 13:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 1:56 [PATCH v2] docs: Fix typo in comment Slark Xiao
2022-07-21 2:49 ` Baoquan He
2022-07-21 3:08 ` Slark Xiao
2022-07-21 15:34 ` Baoquan He
2022-07-21 15:41 ` Martin KaFai Lau
[not found] ` <21cac0ea.18f.182218041f7.Coremail.slark_xiao@163.com>
2022-07-21 18:36 ` Jonathan Corbet
2022-07-21 18:40 ` Randy Dunlap
2022-07-21 23:45 ` Baoquan He
2022-07-25 13:52 ` Joe Perches
2022-07-25 13:57 ` William Breathitt Gray [this message]
2022-07-25 19:52 ` Randy Dunlap
2022-07-25 23:12 ` Joe Perches
2022-07-22 9:44 ` Geert Uytterhoeven
2022-07-25 10:55 ` David Howells
2022-07-25 13:32 ` Baoquan He
2022-07-26 1:04 ` Slark Xiao
2022-07-29 1:08 ` Baoquan He
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=Yt6hMD+HIaERgrqg@fedora \
--to=william.gray@linaro.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bhe@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dhowells@redhat.com \
--cc=dyoung@redhat.com \
--cc=haoluo@google.com \
--cc=joe@perches.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kexec@lists.infradead.org \
--cc=kpsingh@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=martin.lau@linux.dev \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=sdf@google.com \
--cc=slark_xiao@163.com \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).