From: Ben Elliston <bje@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: DJ Delorie <dj@delorie.com>,
amacleod@redhat.com, amodra@bigpond.net.au,
binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: New Sanyo Stormy16 relocations
Date: Tue, 17 Dec 2002 14:39:00 -0000 [thread overview]
Message-ID: <m38yyo6zka.fsf@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <15871.31192.305439.813418@casey.transmeta.com>
>>>>> "Doug" == Doug Evans <dje@transmeta.com> writes:
Doug> But, if approval is required, methinks binutils is a better
Doug> place to provide approval for .opc changes (e.g. complaints
Doug> about warnings :-).
I agree that it's a bit counterproductive to post patches to .cpu/.opc
files to the cgen list, since these are just CGEN input files. The
cgen list can/should be used for discussing changes to cgen itself.
Since a .cpu/.opc change _can_ affect all of the applications
involved, how about sending such patches to binutils@, sid@, et al
rather then cgen@?
If we can reach an agreement, it would be a good idea to update the
MAINTAINERS file to reflect the outcome.
Ben
prev parent reply other threads:[~2002-12-17 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1039041358.28757.307.camel@p4>
[not found] ` <20021204225643.GS27956@bubble.sa.bigpond.net.au>
[not found] ` <1039043233.28767.313.camel@p4>
2002-12-16 19:53 ` DJ Delorie
2002-12-16 20:30 ` Alan Modra
2002-12-16 20:48 ` DJ Delorie
2002-12-17 11:25 ` Doug Evans
2002-12-17 11:47 ` DJ Delorie
2002-12-17 11:56 ` Frank Ch. Eigler
2002-12-17 12:09 ` Doug Evans
2002-12-17 12:14 ` Doug Evans
2002-12-18 2:37 ` Andrew Cagney
2002-12-18 7:47 ` Frank Ch. Eigler
2002-12-17 14:39 ` Ben Elliston [this message]
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=m38yyo6zka.fsf@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=amacleod@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dj@delorie.com \
--cc=dje@transmeta.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).