From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH 2/3] howto: Fix typo
Date: Fri, 17 Jan 2020 06:59:10 +0900 [thread overview]
Message-ID: <7d340ee9-e333-67f5-863f-9d81fbf068db@gmail.com> (raw)
In-Reply-To: <805bd7c5-477f-c398-b025-34a630f663f9@gmail.com>
From cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Mon, 13 Jan 2020 16:18:19 +0900
Subject: [PATCH 2/3] howto: Fix typo
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
howto/howto.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/howto/howto.tex b/howto/howto.tex
index bbdacbf1..fe80cca8 100644
--- a/howto/howto.tex
+++ b/howto/howto.tex
@@ -23,7 +23,7 @@ Parallel programming is not as hard as some say, and we hope
that this book makes your parallel-programming projects easier and
more fun.
-In short, where parallel programming once focused on science, research,
+In short, while parallel programming once focused on science, research,
and grand-challenge projects, it is quickly becoming an engineering
discipline.
We therefore examine specific parallel-programming tasks
--
2.17.1
next prev parent reply other threads:[~2020-01-16 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 21:54 [PATCH 0/3] Fix for Fedora31 Akira Yokosawa
2020-01-16 21:57 ` [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 Akira Yokosawa
2020-01-16 21:59 ` Akira Yokosawa [this message]
2020-01-17 3:36 ` [PATCH 2/3] howto: Fix typo Paul E. McKenney
2020-01-18 10:52 ` Akira Yokosawa
2020-01-18 19:42 ` Paul E. McKenney
2020-01-18 23:11 ` Akira Yokosawa
2020-01-19 5:46 ` Paul E. McKenney
2020-01-16 22:00 ` [PATCH 3/3] intro: " Akira Yokosawa
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=7d340ee9-e333-67f5-863f-9d81fbf068db@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.