Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Mark Kettenis <kettenis@gnu.org>
Cc: gdb-patches@sources.redhat.com,
	Joel Sherrill <joel.sherrill@OARcorp.com>,
	 Chris Johns <chrisj@rtems.org>
Subject: Re: m68k-rtems*
Date: Sat, 19 Mar 2005 08:33:00 -0000	[thread overview]
Message-ID: <1111221160.2475.191.camel@mccallum.corsepiu.local> (raw)
In-Reply-To: <1111220442.2475.182.camel@mccallum.corsepiu.local>

On Sat, 2005-03-19 at 09:20 +0100, Ralf Corsepius wrote:
> On Fri, 2005-03-18 at 20:00 +0100, Mark Kettenis wrote:
> >    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...
> 
> We are about to prepare a new rtems-toolchain release and do not want to
Oops, nasty typo: s/do not want/want/g

> base it on the latest current released version instead of some arbitrary
> cvs-snapshots, because cvs-snapshots tend to be in very volatile shape.
> 
> To my knowledge gdb-6.3 is the latest released, current version, so
> keeping the patches in gdb's official cvs, even if there won't be
> another official release helps us to keep our effort small.

For completeness: If you're going to release a new gdb-release in near
future (esp. accompanying GCC-4.0), then using gdb-cvs would also be
fine for us - If not, we'll have to stick to gdb-6.3. 

Ralf




      reply	other threads:[~2005-03-19  8:33 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 ` m68k-rtems* Mark Kettenis
2005-03-19  8:21   ` m68k-rtems* Ralf Corsepius
2005-03-19  8:33     ` Ralf Corsepius [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=1111221160.2475.191.camel@mccallum.corsepiu.local \
    --to=ralf.corsepius@rtems.org \
    --cc=chrisj@rtems.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joel.sherrill@OARcorp.com \
    --cc=kettenis@gnu.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