From: Mark Levedahl <mlevedahl@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Rename V15_MINGW_HEADERS into CYGWIN_OLD_WINSOCK_HEADERS
Date: Sat, 17 Nov 2012 09:38:25 -0500 [thread overview]
Message-ID: <50A7A161.9020805@gmail.com> (raw)
In-Reply-To: <201211170809.50395.tboegi@web.de>
On 11/17/2012 02:09 AM, Torsten Bögershausen wrote:
> See commit 380a4d927bff693c42fc6b22c3547bdcaac4bdc3:
> "Update cygwin.c for new mingw-64 win32 api headers"
> Cygwin up to 1.7.16 uses some header file from the WINE project
> Cygwin 1.7.17 uses some header file from the mingw-64 project
> As the old cygwin (like 1.5) never used mingw,
> the name V15_MINGW_HEADERS is confusing.
> Rename it into CYGWIN_OLD_WINSOCK_HEADERS
>
>
> diff --git a/Makefile b/Makefile
> index c3edf8c..c2ea735 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1089,7 +1089,7 @@ ifeq ($(uname_O),Cygwin)
> NO_SYMLINK_HEAD = YesPlease
> NO_IPV6 = YesPlease
> OLD_ICONV = UnfortunatelyYes
> - V15_MINGW_HEADERS = YesPlease
> + CYGWIN_OLD_WINSOCK_HEADERS = YesPlease
>
WINSOCK is certainly a part of the win32 api implementation, but it is
is the entire win32api that changed, not just the tiny bit dealing with
sockets.
Basically, WINDOWS.h, and everything it includes, and all of the dlls it
touches, and the .o files, changed. Calling it "OLD" is not helpful,
what happens in the future with the next change? The only version info
we really have is the dll version. We are switching between the win32
api implementation shipped with cygwin dll version 1.5.x and the one
that is now current. And, the shift is not tied to any particular cygwin
1.7.x dll version either (there are no cross dependencies between the
win32api implementation and any particular dll in the 1.7.x series, just
a coincidence in time as to what packages got updated when). So my
suggestion in the bike shedding category is to
s/V15_MINGW_HEADERS/CYGWIN_V15_WIN32API/
/end of bike shedding.
If this is really worth a second patch, I'll be happy to send one :^)
Mark
next prev parent reply other threads:[~2012-11-17 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 7:09 [PATCH] Rename V15_MINGW_HEADERS into CYGWIN_OLD_WINSOCK_HEADERS Torsten Bögershausen
2012-11-17 14:38 ` Mark Levedahl [this message]
2012-11-18 7:46 ` Junio C Hamano
2012-11-18 21:16 ` [PATCH] USE CGYWIN_V15_WIN32API as macro to select api for cygwin Mark Levedahl
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=50A7A161.9020805@gmail.com \
--to=mlevedahl@gmail.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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 NNTP newsgroup(s).