From: James Lemke <jim@wasabisystems.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: patch for insight & target stdin
Date: Tue, 10 May 2005 20:36:00 -0000 [thread overview]
Message-ID: <1115757401.24600.18.camel@keel.thelemkes.ca> (raw)
In-Reply-To: <20050510203232.GA10672@nevyn.them.org>
> Insight has its own mailing list and is not part of GDB; I recommend
> you send this to insight@sourceware.org instead.
Oops. I'll re-post there.
--
James Lemke jim@wasabisystems.com Orillia, Ontario
http://www.wasabisystems.com
prev parent reply other threads:[~2005-05-10 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 20:31 James Lemke
2005-05-10 20:32 ` Daniel Jacobowitz
2005-05-10 20:36 ` James Lemke [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=1115757401.24600.18.camel@keel.thelemkes.ca \
--to=jim@wasabisystems.com \
--cc=drow@false.org \
--cc=gdb@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