From: "Slark Xiao" <slark_xiao@163.com>
To: "Baoquan He" <bhe@redhat.com>
Cc: "David Howells" <dhowells@redhat.com>,
corbet@lwn.net, vgoyal@redhat.com, dyoung@redhat.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, william.gray@linaro.org,
peterz@infradead.org, mingo@redhat.com, will@kernel.org,
longman@redhat.com, boqun.feng@gmail.com, tglx@linutronix.de,
bigeasy@linutronix.de, kexec@lists.infradead.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-cachefs@redhat.com
Subject: Re:Re: [PATCH v2] docs: Fix typo in comment
Date: Tue, 26 Jul 2022 09:04:41 +0800 (CST) [thread overview]
Message-ID: <55d366e4.486.1823808de32.Coremail.slark_xiao@163.com> (raw)
In-Reply-To: <Yt6bVIoRa0nIvxei@MiWiFi-R3L-srv>
At 2022-07-25 21:32:04, "Baoquan He" <bhe@redhat.com> wrote:
>On 07/25/22 at 11:55am, David Howells wrote:
>> Baoquan He <bhe@redhat.com> wrote:
>>
>> > sed -i "s/the the /the /g" `git grep -l "the the "`
>>
>> You might want to clarify the first "the" with a preceding boundary marker.
>> There are some English words ending in "the" that can be used as verbs, though
>> I'm not sure you'd find any of them here - clothe for example.
>
>Right. I plan to split this big one into patches corresponding to
>different component as Jonathan suggested, and will consider how to mark
>the first 'the' as you suggested, and wrap Slark's pathces which
>includes typo fix of "then the".
>
>Thanks
>Baoquan
Actually I have committed all changes which were listed in your previous list.
I committed it one by one and checked if any other typo is included.
If possible, you can try other double typo issue like "and and " or "or or" or something else.
Thanks
next prev parent reply other threads:[~2022-07-26 1:06 UTC|newest]
Thread overview: 16+ 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: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
2022-07-25 19:52 ` Randy Dunlap
2022-07-25 23:12 ` Joe Perches
2022-07-22 9:44 ` Geert Uytterhoeven
[not found] ` <YtlyDZEsOZHt6tRs@MiWiFi-R3L-srv>
2022-07-25 10:55 ` David Howells
2022-07-25 13:32 ` Baoquan He
2022-07-26 1:04 ` Slark Xiao [this message]
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=55d366e4.486.1823808de32.Coremail.slark_xiao@163.com \
--to=slark_xiao@163.com \
--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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--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=sdf@google.com \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
--cc=william.gray@linaro.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