From: "Frank Ch. Eigler" <fche@tooth.toronto.redhat.com>
To: cagney@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: Obsolete GDB's m32r support
Date: Tue, 18 Jun 2002 07:06:00 -0000 [thread overview]
Message-ID: <200206181406.g5IE6kb05361@tooth.toronto.redhat.com> (raw)
In-Reply-To: Your message of "Tue, 18 Jun 2002 09:52:30 EDT." <3D0F3B1E.5020308@cygnus.com>
Hi -
> > Can you summarize the technical reasons for this dichotomy of
> > outcomes? In what way does the presence of old targets pose a
> > technical challenge to more modern multiarch'd ones? In other words,
> > what technical reasons exist to not allow old targets to stick around
> > as they are?
>
> The rationale for this move has been discussed on a number of occasions
> in the past, can I recommend a quick search through the e-mail archives
> and a review of that previous debate.
A quick search resulted only in (valid) descriptions of multi-arch
superiority, and dicta that old targets shall convert or die. It
didn't answer my question above. Perhaps you could spare time for
a more specific pointer?
- FChE
next prev parent reply other threads:[~2002-06-18 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 17:25 Andrew Cagney
2002-06-18 6:11 ` Frank Ch. Eigler
2002-06-18 6:52 ` Andrew Cagney
2002-06-18 7:06 ` Frank Ch. Eigler [this message]
2002-06-18 8:42 ` 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=200206181406.g5IE6kb05361@tooth.toronto.redhat.com \
--to=fche@tooth.toronto.redhat.com \
--cc=cagney@redhat.com \
--cc=gdb@sources.redhat.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