From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: kettenis@chello.nl
Cc: gdb-patches@sources.redhat.com, dj@delorie.com
Subject: Re: [PATCH] Add two new OS ABI variants
Date: Sun, 09 Jun 2002 10:10:00 -0000 [thread overview]
Message-ID: <8011-Sun09Jun2002200908+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <200206091651.g59GpjQ40007@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Sun, 9 Jun 2002 18:51:45 +0200 (CEST))
> Date: Sun, 9 Jun 2002 18:51:45 +0200 (CEST)
> From: Mark Kettenis <kettenis@chello.nl>
>
> But does it make
> sense to use GDB_OSABI_DJGPP when all function names still use go32
> somewhere in their name? Do you have any plans for renaming those?
I don't mind renaming go32-nat.c into djgpp-nat.c, but renaming a
file in CVS has nasty side effects, and I'm not sure we have a reason
good enough to suffer those side effects.
But a new constant, if we name it DJGPP from day one, has no such
adverse consequences.
prev parent reply other threads:[~2002-06-09 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 8:13 Mark Kettenis
2002-06-09 9:40 ` Eli Zaretskii
2002-06-09 9:51 ` Mark Kettenis
2002-06-09 10:10 ` Eli Zaretskii [this message]
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=8011-Sun09Jun2002200908+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=dj@delorie.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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