From: zhouzhouyi@gmail.com
To: paulmck@kernel.org, akiyks@gmail.com, perfbook@vger.kernel.org
Cc: Zhouyi Zhou <zhouyi.zhou@ucas.com.cn>,
Zhouyi Zhou <zhouzhouyi@gmail.com>
Subject: [PATCH -perfbook] toolsoftrade: fix a typo: manpages should be man pages
Date: Sat, 30 Dec 2023 16:59:29 +0800 [thread overview]
Message-ID: <1703926769-5124-1-git-send-email-zhouzhouyi@gmail.com> (raw)
From: Zhouyi Zhou <zhouyi.zhou@ucas.com.cn>
According to [1][2], manpages should be man pages or man-pages.
[1] https://en.wikipedia.org/wiki/Man_page
[2] https://www.kernel.org/doc/man-pages/
Signed-off-by: Zhouyi Zhou<zhouzhouyi@gmail.com>
---
toolsoftrade/toolsoftrade.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index 645ee74b..097c18d6 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -308,7 +308,7 @@ Parent process sees x=0
(such as \co{mmap()} and \co{shmget()}).
In the meantime, there are any number of textbooks that cover
these primitives in great detail,
- and the truly motivated can read manpages, existing parallel
+ and the truly motivated can read man pages, existing parallel
applications using these primitives, as well as the
source code of the Linux-kernel implementations themselves.
--
2.34.1
next reply other threads:[~2023-12-30 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 8:59 zhouzhouyi [this message]
2023-12-30 23:59 ` [PATCH -perfbook] toolsoftrade: fix a typo: manpages should be man pages Paul E. McKenney
2023-12-31 0:11 ` Zhouyi Zhou
2023-12-31 0:25 ` Paul E. McKenney
2024-01-01 1:00 ` Akira Yokosawa
2024-01-01 1:51 ` Zhouyi Zhou
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=1703926769-5124-1-git-send-email-zhouzhouyi@gmail.com \
--to=zhouzhouyi@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
--cc=zhouyi.zhou@ucas.com.cn \
/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).