From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] formal: Trivial typo fixes
Date: Tue, 19 Jul 2016 08:10:24 -0700 [thread overview]
Message-ID: <20160719151024.GU7094@linux.vnet.ibm.com> (raw)
In-Reply-To: <ee5270b0-78c0-ae91-6a93-336968af2589@gmail.com>
On Tue, Jul 19, 2016 at 11:42:13PM +0900, Akira Yokosawa wrote:
> >From aefb442330115d2af25f532fcd725ed4c06e6908 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Tue, 19 Jul 2016 23:30:18 +0900
> Subject: [PATCH] formal: Trivial typo fixes
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Thank you!
I queued both this and the quick-quiz explanation. I wordsmithed
the explanation as shown below.
Thanx, Paul
> ---
> formal/formal.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/formal/formal.tex b/formal/formal.tex
> index 0e5fef3..ed9d7a3 100644
> --- a/formal/formal.tex
> +++ b/formal/formal.tex
> @@ -126,7 +126,7 @@ The larger overarching software construct is of course validated by testing.
> because the rate of change is just too great.
> Furthermore, although the L4 microkernel is a large software
> artifact from the viewpoint of formal verification, it is tiny
> - compared to the a great number of projects, including LLVM,
> + compared to a great number of projects, including LLVM,
> gcc, the Linux kernel, Hadoop, MongoDB, and a great many others.
>
> Although formal verification is finally starting to show some
> @@ -171,4 +171,4 @@ All else being equal, a simpler implementation is much better than
> a mechanical proof for a complex implementation!
>
> And the open challenge to those working on formal verification techniques
> -and systems is prove this summary wrong!
> +and systems is to prove this summary wrong!
> --
> 1.9.1
>
------------------------------------------------------------------------
commit c2260df4e50e2384d99713f8e07b62275e1aa7b2
Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Date: Tue Jul 19 08:08:08 2016 -0700
Wordsmith switching between quick-quiz questions and answers
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
diff --git a/howto/howto.tex b/howto/howto.tex
index 68ed47d919b0..efb570c9d066 100644
--- a/howto/howto.tex
+++ b/howto/howto.tex
@@ -209,12 +209,12 @@ Here are a few possible strategies:
Note that as of mid-2016 the quick quizzes are hyperlinked
to the answers and vice versa.
-Click either the ``Quick Quiz'' headings or the small squares
-to move back and forth between quiz and answer.
-Also note that the white squares at the end of answers are
-linked to the black squares at the end of quizzes.
-If you want to continue reading text after the end of quizzes,
-white squares would be of your choice.
+Click either the ``Quick Quiz'' heading or the small black square
+to move to the beginning of the answer.
+From the answer, click on the heading or the small black square to
+move to the beginning of the quiz, or, alternatively, click on the
+small white square at the end of the answer to move to the end of the
+corresponding quiz.
} \QuickQuizEnd
In short, if you need a deep
prev parent reply other threads:[~2016-07-19 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 14:42 [PATCH] formal: Trivial typo fixes Akira Yokosawa
2016-07-19 15:08 ` Akira Yokosawa
2016-07-19 15:17 ` Paul E. McKenney
2016-07-19 15:10 ` 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=20160719151024.GU7094@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox