From: Daniel Jacobowitz <drow@false.org>
To: Mark Mitchell <mark@codesourcery.com>,
Simon Richter <Simon.Richter@hogyros.de>,
Richard Earnshaw <rearnsha@gcc.gnu.org>,
GDB <gdb@sources.redhat.com>
Subject: Re: ARM RDI
Date: Fri, 09 Dec 2005 17:24:00 -0000 [thread overview]
Message-ID: <20051209172347.GA16076@nevyn.them.org> (raw)
In-Reply-To: <20051129180326.GA29028@nevyn.them.org>
On Tue, Nov 29, 2005 at 01:03:26PM -0500, Daniel Jacobowitz wrote:
> On Tue, Nov 29, 2005 at 09:54:07AM -0800, Mark Mitchell wrote:
> > Daniel Jacobowitz wrote:
> >
> > > There are a number of other ways to use RDI besides rdi-share.
> >
> > Indeed.
> >
> > Some of the board vendors also ship GDB<->RDI converters. As you say, I
> > have very little confidence that the current rdi-share actually works
> > with most things.
> >
> > If consensus has been reached to remove rdi-share, may I post a patch
> > for review? Or, if we don't think we can get that consensus, how about
> > at least a patch to make it a configure-time option, off by default?
>
> Consensus can't be reached in one day :-)
>
> Let's come back to this next week, please.
Only Simon objected, and I haven't seen a reply to either Richard's or
my responses to him. Richard (the ARM port maintainer) and Andrew
(second-hand via Richard) were in favor. Anyone else have comments?
Otherwise, next week I intend to remove the rdi-share subdirectory and
its supporting code.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-09 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 3:14 Mark Mitchell
2005-11-29 12:01 ` Richard Earnshaw
2005-11-29 14:12 ` Daniel Jacobowitz
2005-11-29 14:20 ` Simon Richter
2005-11-29 14:27 ` Richard Earnshaw
2005-11-29 17:54 ` Daniel Jacobowitz
2005-11-29 18:03 ` Mark Mitchell
2005-11-29 18:33 ` Daniel Jacobowitz
2005-11-29 18:52 ` Mark Mitchell
2005-12-09 17:24 ` Daniel Jacobowitz [this message]
2005-12-09 17:51 ` Simon Richter
2005-12-09 21:14 ` Stan Shebs
2005-11-29 18:49 ` Jim Blandy
2005-11-29 19:20 ` Mark Mitchell
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=20051209172347.GA16076@nevyn.them.org \
--to=drow@false.org \
--cc=Simon.Richter@hogyros.de \
--cc=gdb@sources.redhat.com \
--cc=mark@codesourcery.com \
--cc=rearnsha@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).