From: "Florian Adamus" <florian-adamus@gmx.de>
To: git@vger.kernel.org
Subject: Commiting files larger than 4 GB on Windows
Date: Wed, 15 Mar 2017 14:00:54 +0100 [thread overview]
Message-ID: <trinity-9f703269-6f73-4f6d-b90b-45e09e1c094c-1489582854278@3capp-gmx-bs66> (raw)
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 reply other threads:[~2017-03-15 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 13:00 Florian Adamus [this message]
2017-03-15 13:48 ` Commiting files larger than 4 GB on Windows Thomas Braun
2017-03-15 15:59 ` Jeff King
2017-03-15 16:13 ` Jeff King
2017-03-15 18:23 ` Thomas Braun
2017-03-15 21:15 ` Torsten Bögershausen
2017-03-15 21:29 ` Junio C Hamano
2017-03-17 5:29 ` Torsten Bögershausen
2017-03-18 13:03 ` Thomas Braun
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=trinity-9f703269-6f73-4f6d-b90b-45e09e1c094c-1489582854278@3capp-gmx-bs66 \
--to=florian-adamus@gmx.de \
--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.
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).