linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
	Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: [PATCH] Documentation: editing fixes in test-suite
Date: Mon, 22 Jan 2018 07:31:18 -0800	[thread overview]
Message-ID: <20180122153118.GA1233@localhost> (raw)
In-Reply-To: <5bf3731a-c3be-e94e-2aaf-4c443e6ed870@infradead.org>

On Sun, Jan 21, 2018 at 09:38:39PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Fix typos, grammar, punctuation, and spelling in Documentation/test-suite.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> Cc: Josh Triplett <josh@joshtriplett.org>

Reviewed-by: Josh Triplett <josh@joshtriplett.org>

>  Documentation/test-suite |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> --- sprs-2018-0119.orig/Documentation/test-suite
> +++ sprs-2018-0119/Documentation/test-suite
> @@ -35,7 +35,7 @@ check-output-start / check-output-end (o
>  
>  check-output-ignore / check-error-ignore (optional)
>  	Don't check the expected output (stdout or stderr) of check-command
> -	(usefull when this output is not comparable or if you're only interested
> +	(useful when this output is not comparable or if you're only interested
>  	in the exit value).
>  	By default this check is done.
>  
> @@ -54,8 +54,8 @@ check-output-excludes: <pattern> (option
>  	must contains none of the patterns.
>  
>  check-output-pattern-<nbr>-times: <pattern> (optional)
> -	Similar than the contains/excludes her above, but with full control
> -	of the number of times the pattern should occurs in the output.
> +	Similar to the contains/excludes above, but with full control
> +	of the number of times the pattern should occur in the output.
>  
>  	Using test-suite
>  	~~~~~~~~~~~~~~~~
> @@ -84,7 +84,7 @@ cmd:
>  	"sparse $file".
>  
>  The output of the test-suite format command can be redirected into the
> -test case to create a test-suite formated file.
> +test case to create a test-suite formatted file.
>  
>  $ ./test-suite format bad-assignment.c Assignment >> bad-assignment.c
>  $ cat !$
> 
> 

  parent reply	other threads:[~2018-01-22 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22  5:38 [PATCH] Documentation: editing fixes in test-suite Randy Dunlap
2018-01-22  5:48 ` Luc Van Oostenryck
2018-01-22 15:31 ` Josh Triplett [this message]
2018-01-23 10:59 ` Christopher Li

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=20180122153118.GA1233@localhost \
    --to=josh@joshtriplett.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).