From: Markus Deuling <deuling@de.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>, Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [rfc] [01/12] Get rid of current_gdbarch in aix-thread.c
Date: Mon, 06 Aug 2007 08:07:00 -0000 [thread overview]
Message-ID: <46B6D654.7070800@de.ibm.com> (raw)
In-Reply-To: <usl70bvhd.fsf@gnu.org>
Eli Zaretskii schrieb:
>
> In that case, I'd prefer to rephrase the log entry as follows:
>
> Use get_regcache_arch or get_frame_arch to get at the current
> architecture by regcache or by frame, respectively.
>
Thank you Eli and Jim. I'll redo the ChangeLog and repost the patches.
As discussed with Joel, we'll commit these patches after 6.7 branch.
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
prev parent reply other threads:[~2007-08-06 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 12:11 Markus Deuling
2007-08-03 12:48 ` Eli Zaretskii
2007-08-03 13:03 ` Markus Deuling
2007-08-03 13:26 ` Eli Zaretskii
2007-08-06 8:07 ` Markus Deuling [this message]
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=46B6D654.7070800@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=uweigand@de.ibm.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