On Wed, Mar 02, 2022 at 06:03:46PM +0000, Skybuck Flying wrote: >> Search for "4GB" in this blog post [1] which discusses the GfW 2.35 release >> notes. >> >> 1. https://github.blog/2022-01-24-highlights-from-git-2-35/
> Thanks for the update, however I don't see how this could effect git > checkout of linux kernel, since most linux source files are only a few > kilobytes... Because Git has several data storage/transfer optimization tricks. One of them is using of so-called "pack files" (basically that's the behind-the-scenes mechanism that allows Git to remain fast and have modest storage requirements while its data model states that each commit is a snapshot of the whole project). Pack files are used for both storing stuff on the filesystem, and for data transfer; they basically are gzipped archives with added index files for fast random access to the contained data. My take is that processing of such a pack file hits some limit of the current GfW implementation, which has nothing to do with the OS limits (given that up-to-date API calls are used). While I think such problems were actually solved some time ago, some may still remain. In any case, it's hard to say something w/o proper bug report - either in the project's tracker of at least on the git-for-windows mailing list. By the way, do you use a 64-bit install? If, for some reason, you're using a 32-bit version, the limit of circa 4 GB (actaually lower) will be "native". -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/20220303104249.7b2ckatvx52rg4mj%40carbon.
