Skip to contentSkip to conversation

Fixed: typo in pycocci.1

PATCH New Masanari Iida 2 participants 8 messages Jul 16, 2016 – Jul 17, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 Fixed: typo in pycocci.1

This patch fix 3 typos found in docs/pycocci.1

---
 docs/pycocci.1 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
docs/pycocci.1 +2 -2
index 8d94d23aae0c..46d500f56a9a 100644
@@ -81,7 +81,7 @@ can typically display differences better.
 default given that at least for Linux kernel development some C files tend to
 include headers in paths only specified by a target's Makefile through
 utilities such as subdir-ccflags or ccflags-y making it difficult to ensure
-all required header files are read by Coccinelle. We are agressive with
+all required header files are read by Coccinelle. We are aggressive with
 headers search and inclusion.
 
 A default timeout of 120 seconds is used by default. Not using a timeout
@@ -188,7 +188,7 @@ used to apply the <SmPL-patch.cocci> ("pycocci-smpl-8-random-chars"). \fBpycocci
 display name of the newly created branches and finally provide the
 output of \fBgit diff --stat <pycocci-patch-8-random-chars>..<pycocci-smpl-8-random-chars>\fP. You should see
 no changes, and therefore a \fBperfect SmPL patch equivalence\fP, when the diffstat
-on the ouput shows no changes. The way to interpet a positive diffstat is that
+on the output shows no changes. The way to interpret a positive diffstat is that
 the <SmPL-patch.cocci> is introducing more changes than the patch series. The
 way to interpret a negative diffstat is that the <SmPL-patch.cocci> is lacking
 some changes in place on the patch series. \fBpycocci\fP will use \fBgit rev-parse --toplevel\fP
Signature · 1 line
2.9.2.277.g2949358
#1 lore raw

PATCH 2/2 Fixed : typo in spatch.1.in

This patch fix a spelling typo in docs/spatch.1.in

---
 docs/spatch.1.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
docs/spatch.1.in +1 -1
index dccf6fca4b51..9e72eb1e7821 100644
@@ -404,7 +404,7 @@ convert ifdef to if (experimental)
 \fB\-\-noadd\-typedef\-root\fR
 .TP
 \fB\-\-disallow\-nested\-exps\fR
-disallow an expresion pattern from matching a term and its subterm
+disallow an expression pattern from matching a term and its subterm
 .HP
 \fB\-\-disable\-worth\-trying\-opt\fR
 .HP
Signature · 1 line
2.9.2.277.g2949358
#2 lore raw

PATCH 1/2 Fixed: typo in pycocci.1

In reply to Masanari Iida

Thank you for your contributions. Could you resend with a Signed-off-by:
as described at the end of the file readme.txt in the Coccinelle source code tree?

thanks,
julia

Quoted 31 lines · Masanari Iida

This patch fix 3 typos found in docs/pycocci.1

---
 docs/pycocci.1 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
docs/pycocci.1 +2 -3
index 8d94d23aae0c..46d500f56a9a 100644
@@ -81,7 +81,7 @@ can typically display differences better.
 default given that at least for Linux kernel development some C files tend to
 include headers in paths only specified by a target's Makefile through
 utilities such as subdir-ccflags or ccflags-y making it difficult to ensure
-all required header files are read by Coccinelle. We are agressive with
+all required header files are read by Coccinelle. We are aggressive with
 headers search and inclusion.
 
 A default timeout of 120 seconds is used by default. Not using a timeout
@@ -188,7 +188,7 @@ used to apply the <SmPL-patch.cocci> ("pycocci-smpl-8-random-chars"). \fBpycocci
 display name of the newly created branches and finally provide the
 output of \fBgit diff --stat <pycocci-patch-8-random-chars>..<pycocci-smpl-8-random-chars>\fP. You should see
 no changes, and therefore a \fBperfect SmPL patch equivalence\fP, when the diffstat
-on the ouput shows no changes. The way to interpet a positive diffstat is that
+on the output shows no changes. The way to interpret a positive diffstat is that
 the <SmPL-patch.cocci> is introducing more changes than the patch series. The
 way to interpret a negative diffstat is that the <SmPL-patch.cocci> is lacking
 some changes in place on the patch series. \fBpycocci\fP will use \fBgit rev-parse --toplevel\fP
--

2.9.2.277.g2949358

#3 lore raw

PATCH 1/4 Fixed: typo in pycocci.1

This patch fix 3 typos found in docs/pycocci.1

---
 docs/pycocci.1 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
docs/pycocci.1 +2 -2
index 8d94d23aae0c..46d500f56a9a 100644
@@ -81,7 +81,7 @@ can typically display differences better.
 default given that at least for Linux kernel development some C files tend to
 include headers in paths only specified by a target's Makefile through
 utilities such as subdir-ccflags or ccflags-y making it difficult to ensure
-all required header files are read by Coccinelle. We are agressive with
+all required header files are read by Coccinelle. We are aggressive with
 headers search and inclusion.
 
 A default timeout of 120 seconds is used by default. Not using a timeout
@@ -188,7 +188,7 @@ used to apply the <SmPL-patch.cocci> ("pycocci-smpl-8-random-chars"). \fBpycocci
 display name of the newly created branches and finally provide the
 output of \fBgit diff --stat <pycocci-patch-8-random-chars>..<pycocci-smpl-8-random-chars>\fP. You should see
 no changes, and therefore a \fBperfect SmPL patch equivalence\fP, when the diffstat
-on the ouput shows no changes. The way to interpet a positive diffstat is that
+on the output shows no changes. The way to interpret a positive diffstat is that
 the <SmPL-patch.cocci> is introducing more changes than the patch series. The
 way to interpret a negative diffstat is that the <SmPL-patch.cocci> is lacking
 some changes in place on the patch series. \fBpycocci\fP will use \fBgit rev-parse --toplevel\fP
Signature · 1 line
2.9.2.277.g2949358
#4 lore raw

PATCH 2/4 Fixed : typo in spatch.1.in

This patch fix a spelling typo in docs/spatch.1.in

---
 docs/spatch.1.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
docs/spatch.1.in +1 -1
index dccf6fca4b51..9e72eb1e7821 100644
@@ -404,7 +404,7 @@ convert ifdef to if (experimental)
 \fB\-\-noadd\-typedef\-root\fR
 .TP
 \fB\-\-disallow\-nested\-exps\fR
-disallow an expresion pattern from matching a term and its subterm
+disallow an expression pattern from matching a term and its subterm
 .HP
 \fB\-\-disable\-worth\-trying\-opt\fR
 .HP
Signature · 1 line
2.9.2.277.g2949358
#5 lore raw

PATCH 3/4 Fixed: typo in cocci_syntax.tex

In reply to Masanari Iida

This patch fix 3 spelling typos found in docs/manual/cocci_syntax.tex

---
 docs/manual/cocci_syntax.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
docs/manual/cocci_syntax.tex +3 -3
index 230b8552031c..d0c9b492acb1 100644
@@ -17,7 +17,7 @@ possible C-language constants.
 
 A square bracket that is surrounded by spaces in the description of a term
 should appear explicitly in the term, as in an array reference.  On the
-other hand, square brackets that surround some other term indicat that the
+other hand, square brackets that surround some other term indicate that the
 presence of that term is optional.
 
 %
@@ -654,7 +654,7 @@ foo()
 \end{tabular}
 \end{center}
 
-Alternatively, the following inidcates that foo() is allowed but optional.
+Alternatively, the following indicates that foo() is allowed but optional.
 This case is typically most useful when all occurrences, if any, of foo()
 prior to c() should be transformed.
 
@@ -1062,7 +1062,7 @@ last matching include that is not under an ifdef in the file.
 
 Each element of a disjunction must be a proper term like an expression, a
 statement, an identifier or a declaration. The constraint on a conjunction
-is similiar.  Thus, the rule on the left below is not a syntactically
+is similar.  Thus, the rule on the left below is not a syntactically
 correct SmPL rule. One may use the rule on the right instead.
 
 \begin{center}
Signature · 1 line
2.9.2.277.g2949358
#6 lore raw

PATCH 4/4 Fixed : typo in spatch_options.tex

In reply to Masanari Iida

This patch fix 5 spelling typos found in
docs/manual/spatch_options.tex

---
 docs/manual/spatch_options.tex | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
docs/manual/spatch_options.tex +5 -5
index ca74a0d5a7d7..190931a2fdcd 100644
@@ -78,7 +78,7 @@ patch file and print out some information about it.}
   containing the semantic patch.  The file name should end in {\tt .cocci}.
 All three options do the same thing.  These options are optional.  If they
 are not used, the single file whose name ends in \texttt{.cocci} is
-assoumed to be the name of the file containing the semantic patch.}
+assumed to be the name of the file containing the semantic patch.}
 
 \rare{-{}-sp ``semantic patch string''}{Specify a semantic match as a
   command-line argument.  See the section ``Command-line semantic match''
@@ -296,7 +296,7 @@ which score file to compare with in the testall run}
 \rare{-{}-parse-error-msg}{Show parsing errors in the C file.}
 
 \rare{-{}-verbose-parsing}{Show parsing errors in the C file, as well as
-  information about attempts to accomodate such errors.  This implicitly
+  information about attempts to accommodate such errors.  This implicitly
   sets {\bf -{}-parse-error-msg.}}
 
 \rare{-{}-parse-handler $\langle$file$\rangle$}{Loads the file containing
@@ -304,8 +304,8 @@ which score file to compare with in the testall run}
   have arguments 1) the line number containing the error, 2) the sequence
   of tokens, the starting and ending line of the function containing the
   error, and array containing the lines of the file containing the error,
-  and the pass of the parser on which the error occurs.  This functyion
-  should then be passed to the fuction {\tt
+  and the pass of the parser on which the error occurs.  This function
+  should then be passed to the function {\tt
     Parse\_c.set\_parse\_error\_function}.}
 
 \rare{-{}-type-error-msg}{Show information about where the C type checker
@@ -603,7 +603,7 @@ stars are used in column 0 rather than {\tt -} and {\tt +}, then the {\tt
 
 \normal{-{}-indent $n$}{The number of spaces to indent, if no other
   information is available.  If this information is not provided, then the
-  default indentation is a tab.  This option is thus particularly relevent
+  default indentation is a tab.  This option is thus particularly relevant
   to projects that don't use tabs.}
 
 \rare{-o $\langle$file$\rangle$}{ This causes the transformed code to be
Signature · 1 line
2.9.2.277.g2949358
#7 lore raw

PATCH 1/4 Fixed: typo in pycocci.1

In reply to Masanari Iida
Quoted 3 lines · Masanari Iida

This patch fix 3 typos found in docs/pycocci.1

Patches 1-4 committed, thanks for your help.

julia

Quoted 30 lines
---
 docs/pycocci.1 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
docs/pycocci.1 +2 -3
index 8d94d23aae0c..46d500f56a9a 100644
@@ -81,7 +81,7 @@ can typically display differences better.
 default given that at least for Linux kernel development some C files tend to
 include headers in paths only specified by a target's Makefile through
 utilities such as subdir-ccflags or ccflags-y making it difficult to ensure
-all required header files are read by Coccinelle. We are agressive with
+all required header files are read by Coccinelle. We are aggressive with
 headers search and inclusion.
 
 A default timeout of 120 seconds is used by default. Not using a timeout
@@ -188,7 +188,7 @@ used to apply the <SmPL-patch.cocci> ("pycocci-smpl-8-random-chars"). \fBpycocci
 display name of the newly created branches and finally provide the
 output of \fBgit diff --stat <pycocci-patch-8-random-chars>..<pycocci-smpl-8-random-chars>\fP. You should see
 no changes, and therefore a \fBperfect SmPL patch equivalence\fP, when the diffstat
-on the ouput shows no changes. The way to interpet a positive diffstat is that
+on the output shows no changes. The way to interpret a positive diffstat is that
 the <SmPL-patch.cocci> is introducing more changes than the patch series. The
 way to interpret a negative diffstat is that the <SmPL-patch.cocci> is lacking
 some changes in place on the patch series. \fBpycocci\fP will use \fBgit rev-parse --toplevel\fP
--

2.9.2.277.g2949358