From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: RFC: don't call add_target for thread_db_ops
Date: Mon, 05 Aug 2013 16:52:00 -0000 [thread overview]
Message-ID: <87txj484i8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87li4uv6nh.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 25 Jul 2013 12:25:22 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> This removes a few more erroneous calls to add_target. These calls
Tom> end up installing the target in a user-visible way; but these targets
Tom> are all auto-activated and, I think, should never be explicitly
Tom> requested.
Tom> I have no way to test these.
I'm checking this in.
If it causes some problem, please let me know and I will try to fix it up.
I don't anticipate anything though.
Tom
prev parent reply other threads:[~2013-08-05 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 16:37 Tom Tromey
2013-07-03 8:46 ` Pedro Alves
2013-07-25 14:14 ` Tom Tromey
2013-07-25 14:39 ` Pedro Alves
2013-07-25 16:31 ` Tom Tromey
2013-07-25 16:53 ` Pedro Alves
2013-07-25 18:25 ` Tom Tromey
2013-07-26 15:23 ` Ulrich Weigand
2013-08-05 16:52 ` Tom Tromey [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=87txj484i8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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