Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>,
	       gdb-patches@sourceware.org, ambrogino.modigliani@mail.com
Subject: Re: [PATCH 07/23] Fix spelling mistakes in comments in shell scripts
Date: Tue, 22 Nov 2016 16:07:00 -0000	[thread overview]
Message-ID: <84675166-99f4-5752-a185-4a46d45f43d9@redhat.com> (raw)
In-Reply-To: <1479663498-30295-8-git-send-email-ambrogino.modigliani@mail.com>

On 11/20/2016 05:38 PM, Ambrogino Modigliani wrote:
> gdb/ChangeLog:
> 
>         * gdb/contrib/expect-read1.sh: Fix spelling in comments.
>         * gdb/gdb_buildall.sh: Fix spelling in comments.
>         * gdb/gdb_mbuildw.sh: Fix spelling in comments.

Typo "gdb_mbuildw.sh" -> "gdb_mbuild.sh".  :-)

> 
> gdb/testsuite/ChangeLog:
> 
>         * gdb/testsuite/dg-extract-results.sh: Fix spelling in comments.

This file is a copy of gcc's contrib/dg-extract-results.sh.  Could you 
send the fix there?

> 
> ld/ChangeLog:
> 
>         * ld/emulparams/elf32mcore.sh: Fix spelling in comments.

ld changes should go the the binutils list.  See the top level
MAINTAINERS file.

> -# This tool excercise any incomplete reads handling in the testsuite by
> +# This tool exercise any incomplete reads handling in the testsuite by

"This tool exercises".

I pushed this fixed patch below.

From ca3cbe5cd7715d1559d55f8e71be1dd7340f13b1 Mon Sep 17 00:00:00 2001
From: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>
Date: Tue, 22 Nov 2016 16:05:00 +0000
Subject: [PATCH] Fix spelling mistakes in comments in shell scripts

gdb/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * contrib/expect-read1.sh: Fix spelling in comments.
        * gdb_buildall.sh: Fix spelling in comments.
        * gdb_mbuild.sh: Fix spelling in comments.
---
 gdb/ChangeLog               | 6 ++++++
 gdb/contrib/expect-read1.sh | 2 +-
 gdb/gdb_buildall.sh         | 2 +-
 gdb/gdb_mbuild.sh           | 4 ++--
 4 files changed, 10 insertions(+), 4 deletions(-)
 mode change 100644 => 100755 gdb/contrib/expect-read1.sh

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 3257bae..2849067 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,11 @@
 2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>
 
+        * contrib/expect-read1.sh: Fix spelling in comments.
+        * gdb_buildall.sh: Fix spelling in comments.
+        * gdb_mbuild.sh: Fix spelling in comments.
+
+2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>
+
         * configure.ac: Fix spelling in comments.
         * configure: Regenerate.
 
diff --git a/gdb/contrib/expect-read1.sh b/gdb/contrib/expect-read1.sh
old mode 100644
new mode 100755
index cc9d811..5eec0dd
--- a/gdb/contrib/expect-read1.sh
+++ b/gdb/contrib/expect-read1.sh
@@ -15,7 +15,7 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
 
-# This tool excercise any incomplete reads handling in the testsuite by
+# This tool exercises any incomplete reads handling in the testsuite by
 # simulating read always returns just 1 character.
 # Testsuite incompatibilities are tracked as GDB PR testsuite/12649.
 
diff --git a/gdb/gdb_buildall.sh b/gdb/gdb_buildall.sh
index 1fc7b38..ed3ffb5 100644
--- a/gdb/gdb_buildall.sh
+++ b/gdb/gdb_buildall.sh
@@ -103,7 +103,7 @@ builddir=`cd $2 && /bin/pwd` || exit 1
 make=${MAKE:-make}
 MAKE=${make}
 export MAKE
-# We dont want GDB do dump cores.
+# We don't want GDB do dump cores.
 ulimit -c 0
 
 # Just make sure we're in the right directory.
diff --git a/gdb/gdb_mbuild.sh b/gdb/gdb_mbuild.sh
index 08927f1..da0c19a 100755
--- a/gdb/gdb_mbuild.sh
+++ b/gdb/gdb_mbuild.sh
@@ -195,7 +195,7 @@ log ()
 
 
 
-# Warn the user of what is comming, print the list of targets
+# Warn the user of what is coming, print the list of targets
 
 echo "$alltarg"
 echo ""
@@ -273,7 +273,7 @@ do
     then
 	# Iff the build fails remove the final build target so that
 	# the follow-on code knows things failed.  Stops the follow-on
-	# code thinking that a failed rebuild succedded (executable
+	# code thinking that a failed rebuild succeeded (executable
 	# left around from previous build).
 	echo ... ${make} ${keepgoing} ${makejobs} ${target}
 	( ${make} ${keepgoing} ${makejobs} all-gdb || rm -f gdb/gdb gdb/gdb.exe
-- 
2.5.5



-- 
Thanks,
Pedro Alves


  reply	other threads:[~2016-11-22 16:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-20 17:38 [PATCH 00/23] Fix spelling mistakes in comments Ambrogino Modigliani
2016-11-20 17:38 ` [PATCH 01/23] Fix spelling mistakes in comments in C source files (bfd) Ambrogino Modigliani
2016-11-20 17:39 ` [PATCH 02/23] Fix spelling mistakes in comments in C source files (gdb) Ambrogino Modigliani
2016-11-21 15:43   ` Yao Qi
2016-11-22 15:21     ` Pedro Alves
2016-11-20 17:39 ` [PATCH 06/23] Fix spelling mistakes in comments in makefiles Ambrogino Modigliani
2016-11-20 17:39 ` [PATCH 04/23] Fix spelling mistakes in comments in C source files (rest of modules) Ambrogino Modigliani
2016-11-20 17:39 ` [PATCH 08/23] Fix spelling mistakes in comments in Ada source files Ambrogino Modigliani
2016-11-22 16:08   ` Pedro Alves
2016-11-20 17:39 ` [PATCH 03/23] Fix spelling mistakes in comments in C source files (sim) Ambrogino Modigliani
2016-11-20 17:39 ` [PATCH 07/23] Fix spelling mistakes in comments in shell scripts Ambrogino Modigliani
2016-11-22 16:07   ` Pedro Alves [this message]
2016-11-20 17:39 ` [PATCH 05/23] Fix spelling mistakes in comments in configure scripts Ambrogino Modigliani
2016-11-22 15:55   ` Pedro Alves
2016-11-20 17:40 ` [PATCH 09/23] Fix spelling mistakes in comments in Assembler files Ambrogino Modigliani
2016-11-22 16:10   ` Pedro Alves
2016-11-20 17:41 ` [PATCH 21/23] Fix spelling mistakes in comments in .sc files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 10/23] Fix spelling mistakes in comments in Expect scripts Ambrogino Modigliani
2016-11-21 22:23   ` Yao Qi
2016-11-20 17:41 ` [PATCH 11/23] Fix spelling mistakes in comments in XML files Ambrogino Modigliani
2016-11-21 20:41   ` Yao Qi
2016-11-20 17:41 ` [PATCH 15/23] Fix spelling mistakes in comments in .igen files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 23/23] Fix spelling mistakes in comments in .y files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 16/23] Fix spelling mistakes in comments in .in files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 22/23] Fix spelling mistakes in comments in .tbl files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 20/23] Fix spelling mistakes in comments in .opc files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 17/23] Fix spelling mistakes in comments in .inc files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 13/23] Fix spelling mistakes in comments in .def files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 19/23] Fix spelling mistakes in comments in .m4 files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 12/23] Fix spelling mistakes in comments in .cpu files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 18/23] Fix spelling mistakes in comments in .l files Ambrogino Modigliani
2016-11-20 17:41 ` [PATCH 14/23] Fix spelling mistakes in comments in .em files Ambrogino Modigliani

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=84675166-99f4-5752-a185-4a46d45f43d9@redhat.com \
    --to=palves@redhat.com \
    --cc=ambrogino.modigliani@gmail.com \
    --cc=ambrogino.modigliani@mail.com \
    --cc=gdb-patches@sourceware.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