From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Dr.-Ing. Christoph Cullmann" <cullmann@absint.com>
Cc: git@vger.kernel.org
Subject: Re: Bug with corruption on clone/fsck/... with large packs + 64-bit Windows, problem with usage of "long" datatype for sizes/offsets?
Date: Mon, 14 Aug 2017 18:05:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1708141802510.19382@virtualbox> (raw)
In-Reply-To: <1232852793.287524.1502435085656.JavaMail.zimbra@absint.com>
Hi Christoph,
On Fri, 11 Aug 2017, Dr.-Ing. Christoph Cullmann wrote:
> on Windows 64-bit, for a repository having a .pack file > 4GB I get
> during cloning:
The reason is Git's source code that over-uses the `unsigned long`
datatype.
In a nearby-thread, an underappreciated effort by Martin Koegler is
underway to get the ball rolling in getting it fixed. Maybe you can help
making Martin a lot more welcome on the Git mailing list, and maybe even
help getting his patches reviewed and integrated?
Ciao,
Johannes
next prev parent reply other threads:[~2017-08-14 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 7:04 Bug with corruption on clone/fsck/... with large packs + 64-bit Windows, problem with usage of "long" datatype for sizes/offsets? Dr.-Ing. Christoph Cullmann
2017-08-14 16:05 ` Johannes Schindelin [this message]
2017-08-14 17:07 ` Stefan Beller
2017-08-14 18: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=alpine.DEB.2.21.1.1708141802510.19382@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=cullmann@absint.com \
--cc=git@vger.kernel.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).