From: Orjan Friberg <orjan.friberg@axis.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: Multiplexed registers and invalidating the register cache
Date: Thu, 29 Apr 2004 08:09:00 -0000 [thread overview]
Message-ID: <4090B829.1010806@axis.com> (raw)
In-Reply-To: <2914-Wed28Apr2004204005+0300-eliz@gnu.org>
Eli Zaretskii wrote:
>>Date: Wed, 28 Apr 2004 12:43:12 -0400
>>From: Andrew Cagney <cagney@gnu.org>
>>
>>>>>>>+The target's register contents has changed.
>>>>
>>>>>FYI, this should probably read:
>>>>> The target's memory or register contents have [has?] changed.
>>>>>eli?
>>>
>>>
>>>I'm not sure; what is the difference between the two wordings?
>>
>>"have" sounds right (...), hmm. Check dictionary ``/has/ 3rd person
>>_singular_, present of /have/'' [canadian oxford] so "have" is correct.
>
>
> I didn't realize that you were talking only about "has" vs "have"
> (your alternative wording was different in other ways). I agree that
> "have" is correct here.
Ok to commit the below, then? (Or should the event description include
the "memory" part of Andrew's suggestion as well?)
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/doc/ChangeLog,v
retrieving revision 1.406
diff -u -p -r1.406 ChangeLog
--- ChangeLog 26 Apr 2004 09:36:56 -0000 1.406
+++ ChangeLog 29 Apr 2004 08:03:19 -0000
@@ -1,3 +1,7 @@
+2004-04-29 Orjan Friberg <orjanf@axis.com>
+
+ * observer.texi (GDB Observers): Correct spelling.
+
2004-04-26 Orjan Friberg <orjanf@axis.com>
* observer.texi (GDB Observers): Add target_changed event.
Index: observer.texi
===================================================================
RCS file: /cvs/src/src/gdb/doc/observer.texi,v
retrieving revision 1.4
diff -u -p -r1.4 observer.texi
--- observer.texi 26 Apr 2004 09:36:56 -0000 1.4
+++ observer.texi 29 Apr 2004 08:03:19 -0000
@@ -75,5 +75,5 @@ The inferior has stopped for real.
@end deftypefun
@deftypefun void target_changed (struct target_ops *@var{target})
-The target's register contents has changed.
+The target's register contents have changed.
@end deftypefun
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2004-04-29 8:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 11:44 Orjan Friberg
2004-04-14 14:46 ` Daniel Jacobowitz
2004-04-14 16:01 ` Andrew Cagney
2004-04-15 10:46 ` Orjan Friberg
2004-04-15 11:25 ` Orjan Friberg
2004-04-15 15:29 ` Andrew Cagney
2004-04-16 12:51 ` Orjan Friberg
2004-04-16 14:13 ` Daniel Jacobowitz
2004-04-16 14:54 ` Orjan Friberg
2004-04-16 19:15 ` Andrew Cagney
2004-04-19 14:13 ` Orjan Friberg
2004-04-21 16:48 ` Andrew Cagney
2004-04-22 13:58 ` Orjan Friberg
2004-04-22 14:33 ` Andrew Cagney
2004-04-23 11:25 ` Orjan Friberg
2004-04-24 0:03 ` Andrew Cagney
2004-04-23 15:20 ` Orjan Friberg
2004-04-23 17:58 ` Eli Zaretskii
2004-04-26 9:41 ` Orjan Friberg
2004-04-24 0:03 ` Andrew Cagney
2004-04-24 8:30 ` Eli Zaretskii
2004-04-28 16:43 ` Andrew Cagney
2004-04-28 17:40 ` Eli Zaretskii
2004-04-29 8:09 ` Orjan Friberg [this message]
2004-04-29 17:56 ` Eli Zaretskii
2004-04-30 7:39 ` Orjan Friberg
2004-04-26 9:50 ` Orjan Friberg
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=4090B829.1010806@axis.com \
--to=orjan.friberg@axis.com \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--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