From: Will Schmidt <willschm@us.ibm.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
gdb-patches@sources.redhat.com, will_schmidt@vnet.ibm.com
Subject: Re: [PATCH] new support for PPC64 architecture
Date: Tue, 13 May 2003 22:59:00 -0000 [thread overview]
Message-ID: <OF37A2093C.C41B416C-ON86256D25.007DFA36-86256D25.007E3D3B@us.ibm.com> (raw)
Those steps sound good to me. :-)
Elena, were you able to get your build to complete?
willschm@us.ibm.com
Linux on PowerPC-64 Development
IBM Rochester
Jim Blandy
<jimb@redhat.com> To: Will Schmidt/Rochester/IBM@IBMUS
cc: gdb-patches@sources.redhat.com, will_schmidt@vnet.ibm.com, Elena Zannoni
05/13/2003 05:38 <ezannoni@redhat.com>
PM Subject: Re: [PATCH] new support for PPC64 architecture
"Will Schmidt" <willschm@us.ibm.com> writes:
> This patch contains code that provides support for GDB on the PPC64
> architecture. This patch will apply clean on top of the RedHat
> gdb-5.3post-0.20021129.29.src.rpm. (A patch against CVS will
> happen, but not today.. )
Okay --- here are the next steps, as I see them:
- As you say, get the patch to apply and run against current sources.
This can happen without worrying about bringing the patch in line
with current requirements for contributions: multi-arch, using new
interfaces, etc.
- Get a test suite run with those sources that we can use as a
baseline for evaluating subsequent work.
- Worry about multi-arch, new interfaces, etc. This should be pretty
easy going, since both tasks break down into (possibly large) sets
of small, mostly independent changes. It'll be easy to work
incrementally, and share the job.
next reply other threads:[~2003-05-13 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 22:59 Will Schmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 14:34 Will Schmidt
2003-04-17 22:44 Will Schmidt
2003-05-07 20:14 ` Andrew Cagney
2003-05-07 20:37 ` Elena Zannoni
2003-05-07 20:46 ` Daniel Jacobowitz
2003-05-09 21:05 ` Jim Blandy
2003-05-13 22:33 ` Jim Blandy
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=OF37A2093C.C41B416C-ON86256D25.007DFA36-86256D25.007E3D3B@us.ibm.com \
--to=willschm@us.ibm.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=will_schmidt@vnet.ibm.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