From: Andrew Cagney <cagney@gnu.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: [patch/CRIS] Prologue scan bug fixes, return_value implementation
Date: Wed, 03 Mar 2004 18:47:00 -0000 [thread overview]
Message-ID: <40462836.1080706@gnu.org> (raw)
Message-ID: <20040303184700.xySIQzzgO35j8ZOCdsoCfQLl7R9QAx8dHs2PTJQdhDQ@z> (raw)
In-Reply-To: <40460ED4.4040201@axis.com>
> Daniel Jacobowitz wrote:
>
>>
>> As Andrew mentioned, you're the listed maintainer of the CRIS port -
>> you don't need approval for changes to CRIS-specific files. I think
>> that at this point it's appropriate for the branch also.
>
>
> Ah, ok. I'm being overly cautious. Thanks for the clarification.
Yes. Since the absolute worst possible outcome for such a commit is you
breaking the CRIS architecture, it is entirely up to you to decide if
its worth the risk :-)
Andrew
next prev parent reply other threads:[~2004-03-03 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Orjan Friberg
2004-03-03 16:40 ` Orjan Friberg
2004-03-03 16:44 ` Daniel Jacobowitz
2004-03-19 0:09 ` Orjan Friberg
2004-03-03 16:59 ` Orjan Friberg
2004-03-19 0:09 ` Andrew Cagney [this message]
2004-03-03 18:47 ` Andrew Cagney
2004-03-04 9:23 ` Orjan Friberg
2004-03-19 0:09 ` Orjan Friberg
2004-03-19 0:09 ` Daniel Jacobowitz
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=40462836.1080706@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@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