From: Mark Klein <mklein@dis.com>
To: egcs@cygnus.com
Subject: "TARGET_SNAKE" vs. "TARGET_PA89"
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <4.1.19990418162602.00b01d50@garfield.dis.com> (raw)
Message-ID: <19990430231500.FNAU2y7e0mAR-c-_oruVtCBJ435cJuV7KBLFjQjI3HI@z> (raw)
In light of another conversation this week about PA-RISC architectures,
I'd like to add my $.02 about changing 'TARGET_SNAKE' to 'TARGET_PA89'
throughout the code, or to delete it entirely in favor of another
multi-valued switch to handle the various flavors of architecture as
recommended by Jerry, I believe it was. Since Snake was an internal
project name for a specific machine, and since PA1.1/PA89 is the
actual architecture, I'd like to propose the change for consistency's
sake.
Regards,
M.
--
Mark Klein DIS International, Ltd.
http://www.dis.com 415-892-8400
PGP Public Key Available
next reply other threads:[~1999-04-30 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-18 16:32 Mark Klein [this message]
1999-04-19 1:07 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Mark Klein
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=4.1.19990418162602.00b01d50@garfield.dis.com \
--to=mklein@dis.com \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).