Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Replace "Hitachi" and "Mitsubishi" with "Renesas"
Date: Fri, 10 Oct 2003 14:34:00 -0000	[thread overview]
Message-ID: <3F86C356.6070407@redhat.com> (raw)
In-Reply-To: <01e401c38eff$57aa9e70$5169910a@KEI>

> Hello,
> 
> While I was writing a documentation for m32r new remote target,
> I found that there were a lot of "Hitachi" and "Mitsubishi" in
> source files and documentations.
> 
> Since they are now Renesas Technology, I replaced them with
> "Renesas."
> 
> I've committed this as obvious.

Unfortunatly, this one isn't so obvious, sigh!  Should "Hitachi" or
"Mitsubishi" appears in an historic context then that name should be
retained - we need to avoid rewriting history.  For instance:

-Hitachi America, Ltd. sponsored the support for H8/300, H8/500, and
+Renesas America, Ltd. sponsored the support for H8/300, H8/500, and
 Super-H processors.

"Hitachi" (a specific legal entity), and not "Renesas" sponsored the H8
development.  At that time Renesas did not exist.

Similarly, for specific products that didn't survive the merger, I think
it's again better to let  the comments reflect history (Is the E7000
still live?  For the d10v, I've never had success finding anything
public on it and I've tried a number of sources, would you have a pointer?)

I see that you've carefully avoided touching the SH-5.  My hunch that
having the sh4/sh5 split would, in the long run, make lives easier was
correct :-)

enjoy,
Andrew



  reply	other threads:[~2003-10-10 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10  7:23 Kei Sakamoto
2003-10-10 14:34 ` Andrew Cagney [this message]
2003-10-14  4:30   ` Kei Sakamoto

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=3F86C356.6070407@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=sakamoto.kei@renesas.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