From: Yao Qi <yao@codesourcery.com>
To: <jeremy.bennett@embecosm.com>
Cc: <gdb-patches@sourceware.org>, Franck Jullien <franck.jullien@gmail.com>
Subject: Re: [PATCH] Remove doc on OpenRISC 1000
Date: Wed, 20 Mar 2013 10:10:00 -0000 [thread overview]
Message-ID: <514982F1.4080906@codesourcery.com> (raw)
In-Reply-To: <1363700147.23712.277.camel@laria>
[My mail sent yesterday didn't show in the mail archive, so send it again.]
On 03/19/2013 09:35 PM, Jeremy Bennett wrote:
> It is quite likely the GDB code for OpenRISC 1000 was never submitted.
> The whole GNU tool chain was developed around 2000-2002, but only
> binutils ever committed its code. The tool chain is still widely used
> and maintained atwww.opencores.org.
Hi Jeremy,
The patch was submitted in the link I gave in my first mail, but only
the doc bit was approved and committed. I can't tell why the non-doc
bits were not approved.
>
> I've copied Franck Jullien, who is the most active developer of the
> OpenRISC GDB port at present (I was in the past). The alternative to
> deleting the documentation is to submit the port.
If the port can be submitted soon (in 2~3 months maybe?), I am fine to
keep the doc there, because it has been there for 10 years. Otherwise,
I prefer to remove them first, personally.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-03-20 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 3:45 Yao Qi
[not found] ` <1363700147.23712.277.camel@laria>
2013-03-20 10:10 ` Yao Qi [this message]
2013-03-20 13:33 ` Pedro Alves
2013-03-21 12:24 ` Franck Jullien
2013-03-21 19:49 ` Jeremy Bennett
2013-03-22 1:40 ` Yao Qi
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=514982F1.4080906@codesourcery.com \
--to=yao@codesourcery.com \
--cc=franck.jullien@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jeremy.bennett@embecosm.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