From: SeongJae Park <sj38.park@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
paulmck@kernel.org, perfbook@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: Re: [PATCH 4/5] debugging: Remove unnecessary space in a sentence
Date: Sat, 11 Feb 2023 09:05:22 -0800 [thread overview]
Message-ID: <20230211170522.9059-1-sj@kernel.org> (raw)
In-Reply-To: <8e71d5af-7da0-29ce-977a-531800616d68@gmail.com>
Hi Akira,
On Mon, 6 Feb 2023 11:53:54 +0900 Akira Yokosawa <akiyks@gmail.com> wrote:
> On Date: Sun, 5 Feb 2023 10:21:27 -0800, SeongJae Park wrote:
> > From: SeongJae Park <sj38.park@gmail.com>
> >
> > Two spaces are usually used between sentences, but a sentence in
> > debugging is using two spaces inside a sentence. Make it uses only one
> > space for consistency.
>
> FWIW, in perfbook's .tex source files, sentence ending periods must
> be at the end of lines. Violation to this rule is flagged by
> "make punctcheck" now a days.
Thank you for letting me know that. So, this is just a note rather than a
change request to this patch, right? I will make no change for this patch on
the next spin if so.
Thanks,
SJ
>
> Thanks, Akira
>
> >
> > Signed-off-by: SeongJae Park <sj38.park@gmail.com>
> > ---
> > debugging/debugging.tex | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/debugging/debugging.tex b/debugging/debugging.tex
> > index 1903c5db..53c7fb94 100644
> > --- a/debugging/debugging.tex
> > +++ b/debugging/debugging.tex
> > @@ -2153,7 +2153,7 @@ serve four major purposes:
> > against your competitors' offerings.
> > \end{enumerate}
> >
> > -Of course, the only completely fair framework is the intended
> > +Of course, the only completely fair framework is the intended
> > application itself.
> > So why would anyone who cared about fairness in benchmarking
> > bother creating imperfect benchmarks rather than simply
next prev parent reply other threads:[~2023-02-11 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 18:21 [PATCH 0/5] debugging: Trivial fixups SeongJae Park
2023-02-05 18:21 ` [PATCH 1/5] debugging: Use \co{} for 'time' output examples SeongJae Park
2023-02-06 2:31 ` Akira Yokosawa
2023-02-11 17:03 ` SeongJae Park
2023-02-05 18:21 ` [PATCH 2/5] debugging: Use \co{} for 'git' and 'Fixes:' SeongJae Park
2023-02-06 2:38 ` Akira Yokosawa
2023-02-11 17:04 ` SeongJae Park
2023-02-05 18:21 ` [PATCH 3/5] debugging: Use \co{} for rcutorture SeongJae Park
2023-02-06 2:48 ` Akira Yokosawa
2023-02-06 17:40 ` Paul E. McKenney
2023-02-05 18:21 ` [PATCH 4/5] debugging: Remove unnecessary space in a sentence SeongJae Park
2023-02-06 2:53 ` Akira Yokosawa
2023-02-11 17:05 ` SeongJae Park [this message]
2023-02-05 18:21 ` [PATCH 5/5] debugging/debugging: s/remainder of a section/following sections/ SeongJae Park
2023-02-06 3:01 ` Akira Yokosawa
2023-02-06 17:33 ` Paul E. McKenney
2023-02-11 17:06 ` SeongJae Park
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=20230211170522.9059-1-sj@kernel.org \
--to=sj38.park@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
--cc=sj@kernel.org \
/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