diff options
Diffstat (limited to 'doc/bugs/fatal__58___Cannot_handle_files_this_big/comment_3_151e7cf96c7d168e1397d111aa47f279._comment')
-rw-r--r-- | doc/bugs/fatal__58___Cannot_handle_files_this_big/comment_3_151e7cf96c7d168e1397d111aa47f279._comment | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/bugs/fatal__58___Cannot_handle_files_this_big/comment_3_151e7cf96c7d168e1397d111aa47f279._comment b/doc/bugs/fatal__58___Cannot_handle_files_this_big/comment_3_151e7cf96c7d168e1397d111aa47f279._comment new file mode 100644 index 000000000..e6ad551e4 --- /dev/null +++ b/doc/bugs/fatal__58___Cannot_handle_files_this_big/comment_3_151e7cf96c7d168e1397d111aa47f279._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-03-01T14:41:45Z" + content=""" +git (not git-annex) will throw this error if a file size is greater than +`size_t`. + +This bug report seemed to originally concern git add being run on such a +file, but I can't see how git-annex would do that, it doesn't add large +files to git. + +I think that in the case of git-annex status, when it runs git status, that +looks at work tree files, and so falls over if they're large, even if +what's checked into git is a nice small git-annex symlink. This would also +probably affect other places where git looks at worktree files, perhaps git +diff (in v6 repo mode). + +Reopening bug report. +"""]] |