From: Mark Mitchell <mark@codesourcery.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Remove rdi-share
Date: Wed, 18 Jan 2006 03:24:00 -0000 [thread overview]
Message-ID: <43CDB4EF.1040407@codesourcery.com> (raw)
In-Reply-To: <8f2776cb0601162147v597ba8d3ke75006a8ec11224d@mail.gmail.com>
Jim Blandy wrote:
> On 1/16/06, Mark Mitchell <mark@codesourcery.com> wrote:
>
>>As I understand it, consensus has been reached that rdi-share should
>>go away. In addition to removing cruft, this also makes it possible
>>to build an ARM GDB for MinGW; the rdi-share bits did not compile on
>>Windows. I've tested this patch by building an arm-eabi GDB for both
>>x86_64-unknown-linux-gnu and i686-mingw32 hosts.
>
> Should there be a NEWS entry for this?
I'm not sure what the criteria is -- but, in my local NEWS file, I now have:
* REMOVED features
The ARM rdi-share module.
OK with that addition?
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2006-01-18 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 22:34 Mark Mitchell
2006-01-17 5:47 ` Jim Blandy
2006-01-18 3:24 ` Mark Mitchell [this message]
2006-01-20 23:10 ` Daniel Jacobowitz
2006-01-21 1:29 ` 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=43CDB4EF.1040407@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@red-bean.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