From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Fernando Nasser <fnasser@redhat.com>,
Scott Bambrough <sbambrough@zimismobile.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] Zap EXTRA_FRAME_INFO for ARM target
Date: Mon, 21 Jan 2002 12:57:00 -0000 [thread overview]
Message-ID: <20020121125749.W8364@dr-evil.shagadelic.org> (raw)
In-Reply-To: <1020121204528.ZM2093@localhost.localdomain>; from kevinb@redhat.com on Mon, Jan 21, 2002 at 01:45:28PM -0700
On Mon, Jan 21, 2002 at 01:45:28PM -0700, Kevin Buettner wrote:
> > Thinking about it Jason was correct in taking this aproach (I suspect
> > I've done this with other targets). A patch making the single
> > independant change of eliminating EXTRA_FRAME_INFO is mechanical, and as
> > such, can be treated as obvious.
>
...
> I do agree, however, that Jason was correct in his approach for the
> alpha since the alpha target doesn't have any listed maintainers.
Just to be clear... I treated it as obvious since in several e-mails Andrew
has said that the process of multi-arch'ing a target is considered obvious,
and the removal of EXTRA_FRAME_INFO is specifically mentioned in the
description of how to multi-arch a target.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-01-21 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 0:27 Kevin Buettner
2002-01-20 15:16 ` Andrew Cagney
2002-01-21 7:57 ` Fernando Nasser
2002-01-21 8:30 ` Richard Earnshaw
2002-01-21 12:46 ` Kevin Buettner
2002-01-21 12:57 ` Jason R Thorpe [this message]
2002-01-21 13:29 ` Kevin Buettner
2002-01-21 13:49 ` Andrew Cagney
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=20020121125749.W8364@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=sbambrough@zimismobile.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