From: Mark Kettenis <kettenis@gnu.org>
To: ralf.corsepius@rtems.org
Cc: gdb-patches@sources.redhat.com, joel.sherrill@OARcorp.com,
chrisj@rtems.org
Subject: Re: m68k-rtems*
Date: Fri, 18 Mar 2005 19:01:00 -0000 [thread overview]
Message-ID: <200503181900.j2IJ0i5q014743@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <1111139045.2475.132.camel@mccallum.corsepiu.local> (message from Ralf Corsepius on Fri, 18 Mar 2005 10:44:05 +0100)
From: Ralf Corsepius <ralf.corsepius@rtems.org>
Date: Fri, 18 Mar 2005 10:44:05 +0100
Hi,
The patch below restores m68k-rtems support, which somehow seems to have
gone lost in gdb, some (very long) time ago :).
I'd politely ask you to apply this patch to cvs-head and gdb-6_3-branch.
Checked in on mainline. What's your motivation for having this on
gdb-6_3-branch? That branch is basically dead now...
Mark
next prev parent reply other threads:[~2005-03-18 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 9:44 m68k-rtems* Ralf Corsepius
2005-03-18 19:01 ` Mark Kettenis [this message]
2005-03-19 8:21 ` m68k-rtems* Ralf Corsepius
2005-03-19 8:33 ` m68k-rtems* Ralf Corsepius
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=200503181900.j2IJ0i5q014743@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=chrisj@rtems.org \
--cc=gdb-patches@sources.redhat.com \
--cc=joel.sherrill@OARcorp.com \
--cc=ralf.corsepius@rtems.org \
/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