From: Mark Kettenis <kettenis@science.uva.nl>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: gdbserver/{<foo>,<os>,<bar>}.c?; Was: [rfa] gdbserver overhaul
Date: Sun, 21 Oct 2001 04:02:00 -0000 [thread overview]
Message-ID: <s3iofn1w94e.fsf@soliton.wins.uva.nl> (raw)
In-Reply-To: <3BCDDD47.2010805@cygnus.com>
Andrew Cagney <ac131313@cygnus.com> writes:
> > I used lnx-, because they needed to be 8.3 unique - isn't that
> > preferred to an entry in fnmatch.* (?)? They were originally
> > low-linux-*.c instead, which was much more logical to me. I'll go back
> > to that if the 8.3 conflicts are not a concern.
>
> I think the ``keep it consistent and call it linux'' concern overrides
> the 8.3 concern.
It just occured to me that if we really want to use a consistent
naming scheme, we should probably use CPU-OS-low.c
(i.e. i386-linux-low.c) just like we have CPU-OS-tdep.c and
CPU-OS-nat.c.
next prev parent reply other threads:[~2001-10-21 4:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 13:15 Daniel Jacobowitz
2001-10-14 18:13 ` Andrew Cagney
2001-10-14 18:44 ` Daniel Jacobowitz
2001-10-16 21:12 ` Andrew Cagney
2001-10-16 21:24 ` Daniel Jacobowitz
2001-10-16 21:09 ` Andrew Cagney
2001-10-16 21:23 ` Daniel Jacobowitz
2001-10-17 4:45 ` Eli Zaretskii
2001-10-17 9:06 ` Andrew Cagney
2001-10-17 10:57 ` Daniel Jacobowitz
2001-10-17 12:34 ` gdbserver/{<foo>,<os>,<bar>}.c?; Was: " Andrew Cagney
2001-10-17 13:39 ` Daniel Jacobowitz
2002-09-27 15:35 ` Andrew Cagney
2002-09-27 15:49 ` Andrew Cagney
2001-10-18 1:11 ` Eli Zaretskii
2001-10-18 9:30 ` Andrew Cagney
2001-10-18 12:36 ` Eli Zaretskii
2001-10-18 11:59 ` Andrew Cagney
2001-10-18 12:08 ` Daniel Jacobowitz
2001-10-21 4:02 ` Mark Kettenis [this message]
2001-10-21 9:15 ` Andrew Cagney
2001-10-17 15:17 ` Daniel Jacobowitz
2001-10-18 14:28 ` Andrew Cagney
2001-10-18 17:06 ` Daniel Jacobowitz
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=s3iofn1w94e.fsf@soliton.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.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