From: Johannes Sixt <j.sixt@viscovery•net>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org, Vincent van Ravesteijn <vfr@lyx•org>,
Ramsay Jones <ramsay@ramsay1•demon.co.uk>,
msysGit <msysgit@googlegroups•com>
Subject: Re: What's cooking in git.git (Nov 2011, #03; Sun, 13)
Date: Mon, 14 Nov 2011 08:19:29 +0100 [thread overview]
Message-ID: <4EC0C101.4060001@viscovery.net> (raw)
In-Reply-To: <7vmxbzl5ch.fsf@alter.siamese.dyndns.org>
IMO, these two topics can move forward:
> * vr/msvc (2011-10-31) 3 commits
> - MSVC: Remove unneeded header stubs
> - Compile fix for MSVC: Include <io.h>
> - Compile fix for MSVC: Do not include sys/resources.h
>
> It seems this needs to be rehashed with msysgit folks.
With these patches, git can be built with MSVC. The result is usable,
although a few tests still fail.
> * na/strtoimax (2011-11-05) 3 commits
> - Support sizes >=2G in various config options accepting 'g' sizes.
> - Compatibility: declare strtoimax() under NO_STRTOUMAX
> - Add strtoimax() compatibility function.
>
> It seems this needs to be rehashed with msysgit folks.
There were a few curiosities around strtoimax being present in MinGW or
not, but these have been resolved. Also, whether or not we should define
NO_STRTOUMAX for the MinGW build is an independent matter.
-- Hannes
next prev parent reply other threads:[~2011-11-14 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 4:01 What's cooking in git.git (Nov 2011, #03; Sun, 13) Junio C Hamano
2011-11-14 7:19 ` Johannes Sixt [this message]
2011-11-15 7:27 ` Junio C Hamano
2011-11-14 11:10 ` Jeff King
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=4EC0C101.4060001@viscovery.net \
--to=j.sixt@viscovery$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=msysgit@googlegroups$(echo .)com \
--cc=ramsay@ramsay1$(echo .)demon.co.uk \
--cc=vfr@lyx$(echo .)org \
/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