From: Jason Hatton <jhatton@globalfinishing.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: "René Scharfe" <l.s.r@web.de>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: RE: [PATCH] Prevent git from rehashing 4GBi files
Date: Sat, 7 May 2022 18:10:32 +0000 [thread overview]
Message-ID: <CY4PR16MB1655F08CD03748C491FE4BB9AFC49@CY4PR16MB1655.namprd16.prod.outlook.com> (raw)
In-Reply-To: <CY4PR16MB165501ED1B535592033C76F2AFC49@CY4PR16MB1655.namprd16.prod.outlook.com>
> Philip wrote:
>
> Is this on Git for Windows or a 64 bit Linux?
> There are still some issues on GfW for 2GiB+ files (long Vs long long int).
It was on GfW 64 bit. The Linux 64 bit one seems OK.
Further testing shows that unpatched GfW 64 bit chokes on 4GiB files. Just
use git add and git fsck. At least this patch seems to work on Linux
and works on GfW when using LFS.
--
Jason
next parent reply other threads:[~2022-05-07 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CY4PR16MB165501ED1B535592033C76F2AFC49@CY4PR16MB1655.namprd16.prod.outlook.com>
2022-05-07 18:10 ` Jason Hatton [this message]
[not found] <philipoakley@iee.email>
2022-05-07 18:58 ` [PATCH] Prevent git from rehashing 4GBi files Jason D. Hatton
2022-05-07 2:15 Jason Hatton
[not found] ` <1DFD3E42-3EF3-4420-8E01-748EF3DBE7A1@iee.email>
2022-05-07 15:22 ` René Scharfe
2022-05-10 22:45 ` Philip Oakley
2022-05-11 22:24 ` Philip Oakley
-- strict thread matches above, loose matches on Subject: below --
2022-05-06 17:08 Jason Hatton
2022-05-06 18:32 ` Junio C Hamano
2022-05-06 0:26 Jason Hatton
2022-05-06 4:37 ` Torsten Bögershausen
2022-05-06 10:22 ` Philip Oakley
2022-05-06 16:36 ` Junio C Hamano
2022-05-06 21:17 ` Philip Oakley
2022-05-06 21:23 ` 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
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=CY4PR16MB1655F08CD03748C491FE4BB9AFC49@CY4PR16MB1655.namprd16.prod.outlook.com \
--to=jhatton@globalfinishing.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=philipoakley@iee.email \
/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).