From: "Dave Korn" <dave.korn@artimi.com>
To: <binutils@sourceware.org>
Subject: [PATCH] Fix typo in two binutils testsuite test names.
Date: Tue, 02 May 2006 13:44:00 -0000 [thread overview]
Message-ID: <020701c66dee$8c4b7fc0$a501a8c0@CAM.ARTIMI.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
:) Well, seeing as we're all looking at copy-?.d, and seeing as today there
seem to be a lot of minor nits and cleanups going in, I noticed that 'setting'
was mis-speeeled. Does anyone use these names for automated analysis, or
shall we correct it?
Tested by running the testsuite and seeing that it doesn't go wrong and that
the right text ends up in the sum and log files!
2006-05-02 Dave Korn <dave.korn@artimi.com>
* binutils/testsuite/binutils-all/copy-1.d (name): Correct spelling
of 'setting'.
* binutils/testsuite/binutils-all/copy-1.d (name): Likewise.
cheers,
DaveK
--
Can't think of a witty .sigline today....
[-- Attachment #2: typo-patch.diff --]
[-- Type: application/octet-stream, Size: 1321 bytes --]
Index: binutils/testsuite/binutils-all/copy-1.d
===================================================================
RCS file: /cvs/src/src/binutils/testsuite/binutils-all/copy-1.d,v
retrieving revision 1.1
diff -p -u -r1.1 copy-1.d
--- binutils/testsuite/binutils-all/copy-1.d 26 Apr 2006 13:37:05 -0000 1.1
+++ binutils/testsuite/binutils-all/copy-1.d 2 May 2006 13:37:07 -0000
@@ -1,7 +1,7 @@
#PROG: objcopy
#objdump: -h
#objcopy: --set-section-flags .post_text_reserve=contents,alloc,load,readonly,code
-#name: copy with seting section flags 1
+#name: copy with setting section flags 1
.*: +file format .*
Index: binutils/testsuite/binutils-all/copy-2.d
===================================================================
RCS file: /cvs/src/src/binutils/testsuite/binutils-all/copy-2.d,v
retrieving revision 1.2
diff -p -u -r1.2 copy-2.d
--- binutils/testsuite/binutils-all/copy-2.d 2 May 2006 12:17:30 -0000 1.2
+++ binutils/testsuite/binutils-all/copy-2.d 2 May 2006 13:37:07 -0000
@@ -1,7 +1,7 @@
#PROG: objcopy
#objdump: -h
#objcopy: --set-section-flags foo=contents,alloc,load,code
-#name: copy with seting section flags 2
+#name: copy with setting section flags 2
#source: copytest.s
#not-target: *-*-aout
# Note - we use copytest.s and a section named "foo" rather
next reply other threads:[~2006-05-02 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 13:44 Dave Korn [this message]
2006-05-02 15:34 ` Nick Clifton
2006-05-02 17:48 ` Dave Korn
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='020701c66dee$8c4b7fc0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).