git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
	"Jeff King" <peff@peff.net>,
	mlevedahl@gmail.com, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2012, #03; Tue, 13)
Date: Thu, 15 Nov 2012 20:35:34 +0100	[thread overview]
Message-ID: <50A54406.5080309@web.de> (raw)
In-Reply-To: <50A53CF0.7040809@ramsay1.demon.co.uk>

On 11/15/2012 08:05 PM, Ramsay Jones wrote:
> Torsten Bögershausen wrote:
>>> * ml/cygwin-mingw-headers (2012-11-12) 1 commit
>>>   - Update cygwin.c for new mingw-64 win32 api headers
>>>
>>>   Make git work on newer cygwin.
>>>
>>>   Will merge to 'next'.
>>
>> (Sorry for late answer, I managed to test the original patch minutes before Peff merged it to pu)
>> (And thanks for maintaining git)
>>
>> Is everybody using cygwin happy with this?
>
> I am still on cygwin 1.5.22 and quite happy that this patch does
> not (seem) to cause any problems. ;-P
>
>> I managed to compile on a fresh installed cygwin,
>> but failed to compile under 1.7.7, see below.
>> Is there a way we can achieve to compile git both under "old" and "new" cygwin 1.7 ?
>> Or is this not worth the effort?
>
> Did the cygwin project not bump an api version number somewhere?
>
> ATB,
> Ramsay Jones
Ramsay,
you can run uname -r to see the version number.

I myself haven't fully understood all the consequences,
somewhere between 1.7.7 and 1.7.17 the include files had been changed.

If this has consequences for using e.g. winsock2.dll, I want to know 
myself ;-)

/Torsten

  reply	other threads:[~2012-11-15 19:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 17:52 What's cooking in git.git (Nov 2012, #03; Tue, 13) Jeff King
2012-11-13 20:01 ` Junio C Hamano
2012-11-13 20:45 ` Torsten Bögershausen
2012-11-13 20:48   ` Pyeron, Jason J CTR (US)
2012-11-14  1:18   ` Mark Levedahl
2012-11-14 19:02     ` Jeff King
2012-11-14 21:13       ` Torsten Bögershausen
2012-11-15  0:16         ` Jeff King
2012-11-15  0:19           ` Junio C Hamano
2012-11-15  1:50           ` Mark Levedahl
2012-11-15  1:56             ` Jeff King
2012-11-15  5:54               ` Torsten Bögershausen
2012-11-16 18:52                 ` Junio C Hamano
2012-11-17  7:11                   ` Torsten Bögershausen
2012-11-15 19:05   ` Ramsay Jones
2012-11-15 19:35     ` Torsten Bögershausen [this message]
2012-11-15 23:34       ` Mark Levedahl
2012-11-13 22:57 ` Junio C Hamano

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=50A54406.5080309@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=mlevedahl@gmail.com \
    --cc=peff@peff.net \
    --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).