From: Johannes Sixt <j.sixt@viscovery.net>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>,
Marius Storm-Olsen <mstormo@gmail.com>
Subject: Re: [PATCH 4/4] win32: Improve the conditional inclusion of WIN32 API code
Date: Thu, 05 Nov 2009 08:41:54 +0100 [thread overview]
Message-ID: <4AF281C2.5010504@viscovery.net> (raw)
In-Reply-To: <4AF1D8B9.9040603@ramsay1.demon.co.uk>
Ramsay Jones schrieb:
> Johannes Sixt wrote:
>> It may be that I understand something incorrectly; but then I blame the
>> justification that you gave. In this case, it would be helpful to reword
>> the commit message, and perhaps add some results from your experiments.
>>
>
> The discussion which lead to this patch, including the experiments, can be
> found in the email thread starting here:
>
> http://thread.gmane.org/gmane.comp.version-control.git/129403
>
> (along with some other unrelated stuff; but it's not a long read :)
>
> In the above thread, Marius suggested API_WIN32, but I switched it around, since
> I thought it sounded better! I also thought about GIT_WIN32. Suggestions?
I suggested to treat WIN32 and _WIN32 as synonyms. The commit message
should summarize what you observed in your experiments.
But you can also tell me now why this is not possible. (I recall that your
report about the experiments was rather long; I don't have the time to
read and understand it again and to draw the correct conclusions.)
-- Hannes
prev parent reply other threads:[~2009-11-05 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 19:15 [PATCH 4/4] win32: Improve the conditional inclusion of WIN32 API code Ramsay Jones
2009-11-03 7:41 ` Johannes Sixt
2009-11-04 19:40 ` Ramsay Jones
2009-11-05 7:41 ` Johannes Sixt [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=4AF281C2.5010504@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mstormo@gmail.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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).