From: "Paul E. McKenney" <paulmck@kernel.org>
To: zhouzhouyi@gmail.com
Cc: akiyks@gmail.com, perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook V2] toolsoftrade: fix a typo: manpages should be man pages
Date: Wed, 3 Jan 2024 14:05:55 -0800 [thread overview]
Message-ID: <f722d847-829e-499a-8123-d32cba55edbf@paulmck-laptop> (raw)
In-Reply-To: <1704074187-6886-1-git-send-email-zhouzhouyi@gmail.com>
On Mon, Jan 01, 2024 at 09:56:27AM +0800, zhouzhouyi@gmail.com wrote:
> From: Zhouyi Zhou <zhouzhouyi@gmail.com>
>
> 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>
> ---
> "From:" and "Signed-off-by:" match as suggested by Akira
> Thanks, Zhouyi
I have replaced the previous commit with this one, thank you both!
Thanx, Paul
> --
> 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
>
prev parent reply other threads:[~2024-01-03 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 1:56 [PATCH -perfbook V2] toolsoftrade: fix a typo: manpages should be man pages zhouzhouyi
2024-01-03 22:05 ` Paul E. McKenney [this message]
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=f722d847-829e-499a-8123-d32cba55edbf@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.org \
--cc=zhouzhouyi@gmail.com \
/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).