[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5bd85a7241e6ccac7fe5647cb9cf7ef22b228943.camel@perches.com>
Date: Mon, 25 Jul 2022 06:52:15 -0700
From: Joe Perches <joe@...ches.com>
To: Baoquan He <bhe@...hat.com>, Randy Dunlap <rdunlap@...radead.org>,
Jonathan Corbet <corbet@....net>,
Slark Xiao <slark_xiao@....com>
Cc: kafai <kafai@...com>, vgoyal <vgoyal@...hat.com>,
dyoung <dyoung@...hat.com>, ast <ast@...nel.org>,
daniel <daniel@...earbox.net>, andrii <andrii@...nel.org>,
"martin.lau" <martin.lau@...ux.dev>, song <song@...nel.org>,
yhs <yhs@...com>, "john.fastabend" <john.fastabend@...il.com>,
kpsingh <kpsingh@...nel.org>, sdf <sdf@...gle.com>,
haoluo <haoluo@...gle.com>, jolsa <jolsa@...nel.org>,
"william.gray" <william.gray@...aro.org>,
dhowells <dhowells@...hat.com>, peterz <peterz@...radead.org>,
mingo <mingo@...hat.com>, will <will@...nel.org>,
longman <longman@...hat.com>,
"boqun.feng" <boqun.feng@...il.com>, tglx <tglx@...utronix.de>,
bigeasy <bigeasy@...utronix.de>,
kexec <kexec@...ts.infradead.org>,
linux-doc <linux-doc@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
bpf <bpf@...r.kernel.org>,
linux-cachefs <linux-cachefs@...hat.com>
Subject: Re: [PATCH v2] docs: Fix typo in comment
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@....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'
Powered by blists - more mailing lists