From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
GIT Mailing-list <git@vger.kernel.org>,
tboegi@web.de
Subject: Re: [PATCH RESEND v2] path: Fix a sparse warning
Date: Wed, 29 May 2013 15:46:08 +0200 [thread overview]
Message-ID: <51A606A0.5060101@web.de> (raw)
In-Reply-To: <7vhahn2fz2.fsf@alter.siamese.dyndns.org>
On 2013-05-28 19.04, Junio C Hamano wrote:
>
> Can you tell me what the conclusion on the discussion on your two
> other patches on 'pu'?
>
> * rj/mingw-cygwin (2013-05-08) 2 commits
> - cygwin: Remove the CYGWIN_V15_WIN32API build variable
> - mingw: rename WIN32 cpp macro to GIT_WINDOWS_NATIVE
>
> I stopped keeping track of the discussion and my vague recollection
> was that it is OK for 1.5 but not verified on 1.7 or something?
>
The tests I did under cygwin 1.7 did not show any regression.
/Torsten
next prev parent reply other threads:[~2013-05-29 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 19:24 [PATCH RESEND v2] path: Fix a sparse warning Ramsay Jones
2013-05-28 17:04 ` Junio C Hamano
2013-05-29 13:46 ` Torsten Bögershausen [this message]
2013-05-29 23:57 ` Ramsay Jones
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=51A606A0.5060101@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).