git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Commiting files larger than 4 GB on Windows

From
FAFlorian Adamus <florian-adamus@gmx.de>
Date
Mar 15, 2017, 13:00 UTC
Message-ID
<trinity-9f703269-6f73-4f6d-b90b-45e09e1c094c-1489582854278@3capp-gmx-bs66>
Hello,
I am managing my large files with the git-lfs-extension. Some of them were more than 4GB in size. After deleting one of those files from my working tree and do a normal git checkout I ended up with a somehow crippled file with a size of only 46 MB left.
For testing reasons I tried to commit a 4,3 GB file to my git repository without the LFS extension.
After checking out a different branch and switching back to the branch with the large file, I ended up with the same small file as mentioned before.
I already wrote a bug issues to Git for Windows and I was told that it is a problem with the git source code, which uses unsinged long, where it should use size_t.
For more information on the issue you can check the issue tracker of Git for Windows on github. Issue #1063
Is there a way to fix this problem?
 
best regards
Next: Thomas Braun
Message 1 of 9 in “Commiting files larger than 4 GB on Windows”
  1. Florian AdamusMar 15, 2017
  2. Thomas BraunMar 15, 2017
  3. Jeff KingMar 15, 2017
  4. Jeff KingMar 15, 2017
  5. Thomas BraunMar 15, 2017
  6. Torsten BögershausenMar 15, 2017
  7. Junio C HamanoMar 15, 2017
  8. Torsten BögershausenMar 17, 2017
  9. Thomas BraunMar 18, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.