Added a comment: Your directory depth is too long
authoraloukian <aloukian@web>
Thu, 19 Nov 2015 00:13:21 +0000 (00:13 +0000)
committeradmin <admin@branchable.com>
Thu, 19 Nov 2015 00:13:21 +0000 (00:13 +0000)
doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_2_535016130f3307c8104168e6bb8a583d._comment [new file with mode: 0644]

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 (file)
index 0000000..bda2a40
--- /dev/null
@@ -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.
+"""]]