From: Junio C Hamano <gitster@pobox•com>
To: Ramsay Jones <ramsay@ramsay1•demon.co.uk>
Cc: "Torsten Bögershausen" <tboegi@web•de>, git@vger•kernel.org
Subject: Re: [PATCH RFC] CYGWIN: avoid implicit declaration warning
Date: Mon, 24 Nov 2014 13:44:02 -0800 [thread overview]
Message-ID: <xmqq7fykw9y5.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5473A2D0.5010101@ramsay1.demon.co.uk> (Ramsay Jones's message of "Mon, 24 Nov 2014 21:27:44 +0000")
Ramsay Jones <ramsay@ramsay1•demon.co.uk> writes:
> I updated from cygwin 1.5 to cygwin 1.7 at the beginning of the year.
> Since it is no longer supported, I don't think we need to worry about
> version 1.5. When I said 'old installation' I meant my old version 1.7
> 32-bit installation.
>
>> One netbook was converted from XP to Linux, the other machine needs to be
>> re-installed and CYGWIN 1.5 is no longer available for download.
>>
>> I can confirm that Ramsays patch works with CYGWIN 1.7 32 Bit.
>
> Thanks!
Thanks. So the unconditional version of the patch is good to go, I
take?
next prev parent reply other threads:[~2014-11-24 21:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 14:16 [PATCH RFC] CYGWIN: avoid implicit declaration warning Torsten Bögershausen
2014-11-23 17:12 ` Ramsay Jones
2014-11-23 18:53 ` Junio C Hamano
2014-11-23 23:15 ` Ramsay Jones
2014-11-24 7:20 ` Torsten Bögershausen
2014-11-24 16:00 ` Torsten Bögershausen
2014-11-24 18:29 ` [PATCH] t5000 on Windows: do not mistake "sh.exe" as "sh" Johannes Sixt
2014-11-24 20:02 ` Torsten Bögershausen
2014-11-24 21:27 ` [PATCH RFC] CYGWIN: avoid implicit declaration warning Ramsay Jones
2014-11-24 21:44 ` Junio C Hamano [this message]
2014-11-24 22:59 ` Ramsay Jones
2014-11-24 22:27 ` Ramsay Jones
2014-11-24 22:50 ` Junio C Hamano
2014-11-24 23:04 ` Ramsay Jones
2014-11-24 17:59 ` Jonathan Nieder
2014-11-24 19:17 ` Torsten Bögershausen
2014-11-24 21:41 ` 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=xmqq7fykw9y5.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ramsay@ramsay1$(echo .)demon.co.uk \
--cc=tboegi@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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