From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess
Date: Mon, 24 May 2004 18:55:00 -0000 [thread overview]
Message-ID: <40B244FE.4010805@gnu.org> (raw)
In-Reply-To: <20040524154529.GT7207@tausq.org>
2004-05-24 Randolph Chung <tausq@debian.org>
* thread.c (info_threads_command, thread_apply_all_command)
(thread_apply_command, thread_command, do_captured_thread_select):
Remove HPUXHPPA-specific code.
Ah, yes `obvious', thanks.
Andrew
prev parent reply other threads:[~2004-05-24 18:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 20:40 [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess Randolph Chung
2004-05-19 21:37 ` Joel Brobecker
2004-05-19 21:44 ` Randolph Chung
2004-05-19 22:06 ` Joel Brobecker
2004-05-21 18:48 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney
2004-05-21 19:02 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess Randolph Chung
[not found] ` <40AE6260.2090205@gnu.org>
2004-05-26 5:27 ` Randolph Chung
2004-05-26 13:25 ` Daniel Jacobowitz
2004-05-26 15:35 ` Randolph Chung
2004-05-26 16:48 ` Daniel Jacobowitz
2004-05-26 17:54 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney
2004-05-28 23:43 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess Daniel Jacobowitz
2004-05-31 19:43 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney
2004-05-31 20:43 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess Daniel Jacobowitz
2004-06-01 1:31 ` Andrew Cagney
2004-06-01 1:40 ` Daniel Jacobowitz
2004-06-03 17:41 ` Randolph Chung
2004-06-04 18:26 ` Andrew Cagney
2004-05-24 15:45 ` Randolph Chung
2004-05-24 18:55 ` Andrew Cagney [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=40B244FE.4010805@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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