From: Daniel Jacobowitz <drow@false.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb@sources.redhat.com
Subject: Re: Upcoming target: CRISv32
Date: Sun, 03 Oct 2004 18:44:00 -0000 [thread overview]
Message-ID: <20041003184429.GC10453@nevyn.them.org> (raw)
In-Reply-To: <41541817.3020102@axis.com>
On Fri, Sep 24, 2004 at 02:50:31PM +0200, Orjan Friberg wrote:
> I'm starting to feel pretty confident about my CRISv32 port, and would
> like some advice as to how to proceed. The thing is, the CRISv32
> binutils port won't be submitted for another few weeks. Obviously this
> means that gdb for CRISv32 won't build.
>
> On the other hand, submitting it would have its benefits regarding
> ongoing deprecation etc, and (more importantly) I assume it will be
> easier to get non-architecture specific patches accepted.
>
> If submitting a non-buildable port is frowned upon, then I'd be happy to
> sit on it until the binutils code is in place.
Personally, I would prefer that you wait until it is buildable as-is.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-03 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 12:50 Orjan Friberg
2004-09-24 21:24 ` Andrew Cagney
2004-10-03 18:44 ` Daniel Jacobowitz [this message]
2004-10-11 17:55 ` Orjan Friberg
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=20041003184429.GC10453@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=orjan.friberg@axis.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