Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: HPPA files naming convention...
Date: Mon, 25 Nov 2002 16:56:00 -0000	[thread overview]
Message-ID: <20021126005631.GC23000@gnat.com> (raw)

I find the naming convention for the hppa targets too short for my
liking: - hppah  -> hppa on hpux
        - hppao  -> hppa on osf
        - hppab  -> hppa on bsd

I suggest we transition to a more verbose naming, which should be more
consistent with the other ports I know. For instance, how about
hppa-hpux instead of hppah. I hear a netbsd port will probably be done
in the future, we can then use hppa-netbsd.

We would use this convention for the files in the config/pa directory
(tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb
(hppa-hpux-tdep.c).

The part that is indenpedent of the OS would still stay in hppa (eg
tm-hppa, hppa-tdep.c, etc).

Does this seam like a good idea?
-- 
Joel


             reply	other threads:[~2002-11-26  0:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 16:56 Joel Brobecker [this message]
2002-11-25 16:59 ` Daniel Jacobowitz
2002-11-25 17:08 ` Jason R Thorpe
2002-11-25 22:19 ` Eli Zaretskii
2002-11-26  7:30 ` 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=20021126005631.GC23000@gnat.com \
    --to=brobecker@gnat.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