From: Andrew Cagney <ac131313@redhat.com>
To: Doug Evans <dje@transmeta.com>, brolley@redhat.com
Cc: gdb-patches@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: [PATCH] remove .cpu file copying
Date: Fri, 05 Sep 2003 19:03:00 -0000 [thread overview]
Message-ID: <3F58BE1B.3080902@redhat.com> (raw)
In-Reply-To: <200309051534.IAA17701@casey.transmeta.com>
> Here is the sim patch to accompany my previously posted patch to binutils/cgen
> to pass the path of the .cpu file to cgen.
Sigh, Doug you really need to get that FSF assignment in order, its
what, 4 years now? While this change is long, it does appear obvious -
if someone described the problem to Dave he'd end up with the identical
patch.
> We'll need to coordinate checking in this change with cgen.
> Dave, can you check this in when you're ready? (where "ready" here
> includes receipt of requisite approval, obviously)
> Or someone could give me a one-time authority to check this in ...
I'll assume that Dave will handle it. Dave, remember to modify the
changelog so that it records you making the change, but it comming from
doug.
Andrew
> I've included i960 because it's still in the tree.
> One can either not check this part in because it'll be obsoleted rsn,
> or check this part in.
> [btw, is there a plan to delete sim/i960 from the 6.0 branch?]
>
> 2003-09-05 Doug Evans <dje@casey.transmeta.com>
>
next prev parent reply other threads:[~2003-09-05 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 15:44 Doug Evans
2003-09-05 16:31 ` Doug Evans
2003-09-05 17:22 ` Andrew Cagney
2003-09-05 19:03 ` Andrew Cagney [this message]
2003-09-06 7:05 ` Dave Brolley
[not found] ` <16216.57078.426082.733525@casey.transmeta.com>
[not found] ` <3F58FC5C.90207@redhat.com>
[not found] ` <16217.157.59117.344696@casey.transmeta.com>
2003-09-06 14:13 ` Nick Clifton
[not found] ` <16217.35254.503075.467627@casey.transmeta.com>
2003-09-09 3:42 ` Dave Brolley
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=3F58BE1B.3080902@redhat.com \
--to=ac131313@redhat.com \
--cc=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.com \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).