Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] Fix typo: s/Curiosty Rover/Curiosity Rover/
Date: Tue, 12 Dec 2017 19:24:23 -0800	[thread overview]
Message-ID: <20171213032423.GI7829@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171213021627.25740-1-sj38.park@gmail.com>

On Wed, Dec 13, 2017 at 11:16:27AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Good eyes!  Applied and pushed, thank you!

							Thanx, Paul

> ---
>  formal/regression.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/formal/regression.tex b/formal/regression.tex
> index 4e06cb7..4e8476d 100644
> --- a/formal/regression.tex
> +++ b/formal/regression.tex
> @@ -584,6 +584,6 @@ Just because many of them are poor fit for regression testing does
>  not at all mean that they are useless, in fact,
>  many of them have proven their worth many times over.\footnote{
>  	For but one example, Promela was used to verify the file system
> -	of none other than the Curiosty Rover.
> +	of none other than the Curiosity Rover.
>  	Was \emph{your} formal verification tool used on a Mars rover?}
>  Just not for regression testing.
> -- 
> 2.10.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2017-12-13  3:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  2:16 [PATCH] Fix typo: s/Curiosty Rover/Curiosity Rover/ SeongJae Park
2017-12-13  3:24 ` 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=20171213032423.GI7829@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=perfbook@vger.kernel.org \
    --cc=sj38.park@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