From: aloukian Date: Thu, 19 Nov 2015 00:13:21 +0000 (+0000) Subject: Added a comment: Your directory depth is too long X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~322^2~99 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=170ea995da383c85b30879a41c6c03f29d421ae1;p=git-annex.git Added a comment: Your directory depth is too long --- diff --git a/doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_2_535016130f3307c8104168e6bb8a583d._comment b/doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_2_535016130f3307c8104168e6bb8a583d._comment new file mode 100644 index 0000000000..bda2a400dc --- /dev/null +++ b/doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_2_535016130f3307c8104168e6bb8a583d._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="aloukian" + subject="Your directory depth is too long" + date="2015-11-19T00:13:21Z" + content=""" +I've had a similar problem when the location of my annex was too deep. Windows only allows 256 char filenames. Git annex takes up a fair bit of that by storing files named according to their hash. I worked around the problem by creating my repo at the drive root and then creating a \"junction\" between the place where I wanted it to be and that location. It seems to work now. +"""]]