From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>,
Kai.Tietz@onevision.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Support of gdb for Windows 64 native systems
Date: Mon, 15 Oct 2007 08:58:00 -0000 [thread overview]
Message-ID: <4712A61E.70408@portugalmail.pt> (raw)
In-Reply-To: <20071014222159.GB13096@ednor.casa.cgf.cx>
Christopher Faylor wrote:
>>> Rename a few things, which really aren't cygwin specific, like:
>>> * cygwin_get_dr6 -> win32_get_dr6
>>> * i386-cygwin-tdep.h -> i386-win32-tdep.h
>>> * nm-cygwin.h -> nm-cygming.h
>> I propose we use "windows" instead of either "win32" or "cygming".
>> It seems more descriptive to me, and also avoids the "32", since
>> eventually we might want to add support for 64-bit windows....
>
We better decide if and what to rename them the next time we're
changing them, then.
> I don't really care about this but the "cygming" probably comes from
> similar naming in gcc.
>
Yes.
> I believe that RMS has objections to the name "win32" and "win64", too.
> So, whatever we use, it shouldn't have the abbreviation "win" in it.
>
I thought his objections were about the naming of the operation
system. win32 seems right to me, when we're talking about the
Win32 API. Windows includes other things, like the interix
subsystem, or the NT native API.
Either way, it might seem I was implying it, but you won't see
rename-only patches from me :)
Cheers,
Pedro Alves
next prev parent reply other threads:[~2007-10-14 23:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uprzkkrf7.fsf@gnu.org>
[not found] ` <20071012222842.GD21800@adacore.com>
[not found] ` <20071013024116.GB29152@adacore.com>
[not found] ` <uk5prl27s.fsf@gnu.org>
[not found] ` <20071013154715.GE29152@adacore.com>
[not found] ` <4711021C.8010805@portugalmail.pt>
[not found] ` <20071013205105.GA13789@adacore.com>
[not found] ` <47114BB7.1000501@portugalmail.pt>
[not found] ` <20071014051622.GC13789@adacore.com>
[not found] ` <471200C5.6050609@portugalmail.pt>
2007-10-14 18:03 ` Christopher Faylor
2007-10-14 19:55 ` Pedro Alves
2007-10-14 22:22 ` Christopher Faylor
2007-10-14 23:14 ` Daniel Jacobowitz
2007-10-15 18:54 ` Christopher Faylor
2007-10-15 19:19 ` Daniel Jacobowitz
2007-10-16 0:18 ` Pedro Alves
2007-10-16 4:21 ` Eli Zaretskii
2007-10-16 6:40 ` Christopher Faylor
2007-10-16 11:57 ` Pedro Alves
2007-10-16 12:41 ` Eli Zaretskii
2007-10-16 14:35 ` Christopher Faylor
2007-10-16 14:41 ` Pedro Alves
2007-10-16 15:56 ` Daniel Jacobowitz
2007-10-16 16:13 ` Christopher Faylor
2007-10-16 16:16 ` Eli Zaretskii
2007-10-16 18:23 ` Joel Brobecker
2007-10-16 18:57 ` Ulrich Weigand
2007-10-17 19:47 ` Pedro Alves
2007-10-17 22:00 ` Joel Brobecker
2007-10-18 4:06 ` Pedro Alves
2007-10-18 4:16 ` Eli Zaretskii
2007-10-18 10:07 ` Joel Brobecker
2007-10-18 20:20 ` Eli Zaretskii
2007-10-19 11:48 ` Joel Brobecker
2007-10-19 12:09 ` Daniel Jacobowitz
2007-10-19 12:27 ` Eli Zaretskii
2007-10-16 20:29 ` Pedro Alves
2007-10-14 23:29 ` Pedro Alves
2007-10-15 18:45 ` Christopher Faylor
2007-10-15 23:32 ` Pedro Alves
2007-10-14 21:16 ` Joel Brobecker
2007-10-14 22:22 ` Christopher Faylor
2007-10-15 8:58 ` Pedro Alves [this message]
2007-10-15 18:39 ` Christopher Faylor
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=4712A61E.70408@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=Kai.Tietz@onevision.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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