public inbox for perfbook@vger.kernel.org
 help / color / mirror / Atom feed
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 2/5] debugging: Use \co{} for 'git' and 'Fixes:'
Date: Sat, 11 Feb 2023 09:04:01 -0800	[thread overview]
Message-ID: <20230211170401.8948-1-sj@kernel.org> (raw)
In-Reply-To: <e75a1d50-704f-d2fc-2e2f-3644ddcd27fd@gmail.com>

Hi Akira,

On Mon, 6 Feb 2023 11:38:58 +0900 Akira Yokosawa <akiyks@gmail.com> wrote:

> On Sun,  5 Feb 2023 10:21:25 -0800, SeongJae Park wrote:
> > From: SeongJae Park <sj38.park@gmail.com>
> > 
> > In 'debugging/', 'git' is a command and 'Fixes:' is a string in command
> > output, which usually enclosed via '\co{}', but those are enclosed with
> > '\emph{}'.  Use '\co{}' instead for being more consistent.
> > 
> > Signed-off-by: SeongJae Park <sj38.park@gmail.com>
> > ---
> >  debugging/debugging.tex | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/debugging/debugging.tex b/debugging/debugging.tex
> > index 3104bb95..3ce74469 100644
> > --- a/debugging/debugging.tex
> > +++ b/debugging/debugging.tex
> > @@ -862,8 +862,8 @@ by the author's invalid assumptions, and who might also test the code.
> >  	hackers of harboring???
> >  }\QuickQuizAnswer{
> >  	Those wishing a complete answer to this question are encouraged
> > -	to search the Linux kernel \emph{git} repository for commits
> 
> I often see "Linux kernel git repository" everywhere, and in this case,
> I suppose emphasizing "git" was the author's intention. Paul might have
> a different opinion, though.
> 
> > -	containing the string ``Fixes:''.
> > +	to search the Linux kernel \co{git} repository for commits
> > +	containing the string \co{Fixes:}.
> 
> As this is mentioned as a "string", \qco{} might be a better choice.

Thanks, I will revise so in the next spin.

> 
>         Thanks, Akra
> 
> >  	There were many thousands of them just in the year 2020, including
> >  	fixes for the following invalid assumptions:
> >  

  reply	other threads:[~2023-02-11 17:04 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 [this message]
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
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=20230211170401.8948-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