From: Alexandre Oliva <aoliva@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Remove sh-hms target
Date: Mon, 13 May 2002 21:27:00 -0000 [thread overview]
Message-ID: <orsn4vbbhw.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <15584.19286.75849.849229@localhost.redhat.com>
On May 13, 2002, Elena Zannoni <ezannoni@redhat.com> wrote:
> The sh-hms target wasn't really doing anything different from sh-elf
> for what gdb was concerned. It built exactly the same set of files.
Hmm... AFAIK, sh-hms is a variant of sh-coff, not sh-elf. Shouldn't
it be retained at least as an alias?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-05-14 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 16:25 Elena Zannoni
2002-05-13 21:27 ` Alexandre Oliva [this message]
2002-05-14 6:54 ` Elena Zannoni
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=orsn4vbbhw.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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