From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@kernel.org
Cc: akiyks@gmail.com, perfbook@vger.kernel.org, sj@kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH v3 0/4] debugging: Trivial fixups
Date: Sun, 12 Feb 2023 08:56:26 -0800 [thread overview]
Message-ID: <20230212165630.26268-1-sj38.park@gmail.com> (raw)
Changes from v2
- Fix subject of patch 1 (Akira Yokosawa)
- Remove redundant following sections intro instead of making it
explicit (Akira Yokosawa)
Changes from v1
- Use 'qco{}' for quoted strings (patch 1, 2) (Akira Yokosawa)
- Explicitly distinguish section and subsection (patch 4) (Paul E.
McKeneeny)
-----
This patchset contains trivial fixups for debugging/, which found while
doing Korean translation[1].
[1] https://github.com/sjp38/perfbook-ko_KR
SeongJae Park (4):
debugging: Use \qco{} for 'time' output examples
debugging: Use \co{} and \qco{} for 'git' and 'Fixes:', respectively
debugging: Remove unnecessary space in a sentence
debugging: Remove redundant following sections introduction
debugging/debugging.tex | 23 +++++++++++------------
1 file changed, 11 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2023-02-12 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 16:56 SeongJae Park [this message]
2023-02-12 16:56 ` [PATCH v3 1/4] debugging: Use \qco{} for 'time' output examples SeongJae Park
2023-02-12 16:56 ` [PATCH v3 2/4] debugging: Use \co{} and \qco{} for 'git' and 'Fixes:', respectively SeongJae Park
2023-02-12 16:56 ` [PATCH v3 3/4] debugging: Remove unnecessary space in a sentence SeongJae Park
2023-02-12 16:56 ` [PATCH v3 4/4] debugging: Remove redundant following sections introduction SeongJae Park
2023-02-12 23:57 ` [PATCH v3 0/4] debugging: Trivial fixups Akira Yokosawa
2023-02-13 0:58 ` Paul E. McKenney
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=20230212165630.26268-1-sj38.park@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).