From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fix typo in sparc-tdep.c
Date: Fri, 05 Mar 2004 15:34:00 -0000 [thread overview]
Message-ID: <200403051534.i25FYgNh035582@elgar.kettenis.dyndns.org> (raw)
Repeated word.
Committed,
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* sparc-tdep.c: Fix typo in comment.
Index: sparc-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/sparc-tdep.c,v
retrieving revision 1.150
diff -u -p -r1.150 sparc-tdep.c
--- sparc-tdep.c 4 Mar 2004 10:10:33 -0000 1.150
+++ sparc-tdep.c 5 Mar 2004 15:34:03 -0000
@@ -43,12 +43,11 @@
struct regset;
-/* This file implements the The SPARC 32-bit ABI as defined by the
- section "Low-Level System Information" of the SPARC Compliance
- Definition (SCD) 2.4.1, which is the 32-bit System V psABI for
- SPARC. The SCD lists changes with respect to the origional 32-bit
- psABI as defined in the "System V ABI, SPARC Processor
- Supplement".
+/* This file implements the SPARC 32-bit ABI as defined by the section
+ "Low-Level System Information" of the SPARC Compliance Definition
+ (SCD) 2.4.1, which is the 32-bit System V psABI for SPARC. The SCD
+ lists changes with respect to the origional 32-bit psABI as defined
+ in the "System V ABI, SPARC Processor Supplement".
Note that if we talk about SunOS, we mean SunOS 4.x, which was
BSD-based, which is sometimes (retroactively?) referred to as
WARNING: multiple messages have this Message-ID
From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fix typo in sparc-tdep.c
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <200403051534.i25FYgNh035582@elgar.kettenis.dyndns.org> (raw)
Message-ID: <20040319000900.wLt3usmDad_ERZVLd2Z2ws7PJkjsXe4jVaUb2x8lxwQ@z> (raw)
Repeated word.
Committed,
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* sparc-tdep.c: Fix typo in comment.
Index: sparc-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/sparc-tdep.c,v
retrieving revision 1.150
diff -u -p -r1.150 sparc-tdep.c
--- sparc-tdep.c 4 Mar 2004 10:10:33 -0000 1.150
+++ sparc-tdep.c 5 Mar 2004 15:34:03 -0000
@@ -43,12 +43,11 @@
struct regset;
-/* This file implements the The SPARC 32-bit ABI as defined by the
- section "Low-Level System Information" of the SPARC Compliance
- Definition (SCD) 2.4.1, which is the 32-bit System V psABI for
- SPARC. The SCD lists changes with respect to the origional 32-bit
- psABI as defined in the "System V ABI, SPARC Processor
- Supplement".
+/* This file implements the SPARC 32-bit ABI as defined by the section
+ "Low-Level System Information" of the SPARC Compliance Definition
+ (SCD) 2.4.1, which is the 32-bit System V psABI for SPARC. The SCD
+ lists changes with respect to the origional 32-bit psABI as defined
+ in the "System V ABI, SPARC Processor Supplement".
Note that if we talk about SunOS, we mean SunOS 4.x, which was
BSD-based, which is sometimes (retroactively?) referred to as
next reply other threads:[~2004-03-05 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 15:34 Mark Kettenis [this message]
2004-03-05 20:15 ` Michael Snyder
2004-03-19 0:09 ` Michael Snyder
2004-03-19 0:09 ` Mark Kettenis
2010-12-12 17:50 Mark Kettenis
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=200403051534.i25FYgNh035582@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.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