From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org, gitster@pobox.com
Cc: Johannes Sixt <j6t@kdbg.org>
Subject: [PATCH 0/2] 2GB fixes for Windows
Date: Thu, 5 Mar 2009 17:05:06 +0100 (CET) [thread overview]
Message-ID: <cover.1236268730u.git.johannes.schindelin@gmx.de> (raw)
On Windows, we can actually have files larger than 2 gigabyte, just not
using off_t, but off64_t instead.
This came up as issue 194 on the msysGit tracker, and as I first brushed
the people off saying that it is not an msysGit issue, by way of an
apology, I started working on this myself.
The first patch adds a test for cloning repositories larger than 2
gigabyte, which is disabled by default, since it is quite expensive (both
in terms of time and in terms of space), and since it must fail when the
underlying filesystem does not allow files larger than 2 gigabyte.
The second patch convinces msysGit (AKA the MinGW port of Git) to make use
of the 64-bit file offsets.
Johannes Schindelin (2):
Add an (optional, since expensive) test for >2g clones
MinGW: 64-bit file offsets
compat/mingw.c | 8 +++++---
compat/mingw.h | 5 ++++-
t/t5705-clone-2gb.sh | 45 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 54 insertions(+), 4 deletions(-)
create mode 100755 t/t5705-clone-2gb.sh
next reply other threads:[~2009-03-05 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 16:05 Johannes Schindelin [this message]
2009-03-05 16:05 ` [PATCH 1/2] Add an (optional, since expensive) test for >2g clones Johannes Schindelin
2009-03-05 16:41 ` Jeff King
2009-03-05 16:58 ` Johannes Schindelin
2009-03-05 18:50 ` Jeff King
2009-03-05 23:08 ` Junio C Hamano
2009-03-06 9:48 ` [PATCH v2 1/2] Add an (optional, since expensive) test for >2gb clones Johannes Schindelin
2009-03-06 9:49 ` [PATCH v2 2/2] MinGW: 64-bit file offsets Johannes Schindelin
2009-03-05 16:05 ` [PATCH " Johannes Schindelin
2009-03-05 20:53 ` Johannes Sixt
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=cover.1236268730u.git.johannes.schindelin@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
/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).