From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
Thomas Braun <thomas.braun@virtuell-zuhause.de>,
Florian Adamus <florian-adamus@gmx.de>,
git@vger.kernel.org
Subject: Re: Commiting files larger than 4 GB on Windows
Date: Fri, 17 Mar 2017 06:29:57 +0100 [thread overview]
Message-ID: <2ebd249b-39a4-23c2-13e3-23c91a938313@web.de> (raw)
In-Reply-To: <xmqq4lyudyaq.fsf@gitster.mtv.corp.google.com>
On 15/03/17 22:29, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> The real "show stopper" is at the end.
>> ...
>>
>> ==========================
>> And it seams as if zlib is the limitation here.
>> Unless we include the zlib source code into Git and redefine uLong,
>> is there a nice way around this:
>> ===========================
>>
>>
>> /usr/include/zconf.h:# define uLong z_uLong
>> /usr/include/zconf.h:# define uLongf z_uLongf
>> /usr/include/zconf.h:typedef unsigned long uLong; /* 32 bits or more */
>> /usr/include/zconf.h:typedef uLong FAR uLongf;
> Hmph. Would ef49a7a0 ("zlib: zlib can only process 4GB at a time",
> 2011-06-10) and e01503b5 ("zlib: allow feeding more than 4GB in one
> go", 2011-06-10) help us here, though?
>
That is good news.
I tried to replace all "unsigned long" with size_t and got that compiling
without warnings under Windows 64 bit.
Compiling this on a 32 bit Linux gave lots of warnings..
Converting all unsigned long into is probably an overkill.
Some may stay, some may be converted into off_t, and some size_t.
Does anybody wants to pick this up?
next prev parent reply other threads:[~2017-03-17 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 13:00 Commiting files larger than 4 GB on Windows Florian Adamus
2017-03-15 13:48 ` Thomas Braun
2017-03-15 15:59 ` Jeff King
2017-03-15 16:13 ` Jeff King
2017-03-15 18:23 ` Thomas Braun
2017-03-15 21:15 ` Torsten Bögershausen
2017-03-15 21:29 ` Junio C Hamano
2017-03-17 5:29 ` Torsten Bögershausen [this message]
2017-03-18 13:03 ` Thomas Braun
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ebd249b-39a4-23c2-13e3-23c91a938313@web.de \
--to=tboegi@web.de \
--cc=florian-adamus@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=thomas.braun@virtuell-zuhause.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).