From b5da332429db17ab84e35f79fd2734bbb99084ec Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 2 Dec 2015 13:28:21 -0400 Subject: comment --- ...mment_3_79c66569c22a1280b807a3c21c2cdc4f._comment | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_3_79c66569c22a1280b807a3c21c2cdc4f._comment diff --git a/doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_3_79c66569c22a1280b807a3c21c2cdc4f._comment b/doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_3_79c66569c22a1280b807a3c21c2cdc4f._comment new file mode 100644 index 000000000..c95034fdf --- /dev/null +++ b/doc/bugs/Windows_:_git-annex:_failed_to_read_sha_from_git_write-tree/comment_3_79c66569c22a1280b807a3c21c2cdc4f._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-12-02T17:22:01Z" + content=""" +Windows certianly does cause problems with its short path limits. The +SHA512 hash backend is known to not work at all on windows, for example. + +However, recent versions of git-annex use relative paths to files, so it +shouldn't much matter if they're run in a directory deep in a tree; it'll +refer to '.git/foo' rather than 'c:/verylong/path/to/.git/foo' + +Also, a long path is certianly not the cause of + + DeleteFile ".git\\objects\\pack\\pack-c53ea32e9514b6dda95af1d8d879d91d32240d76.idx": permission denied + +Since the path there is relative, is plenty short to not bother Windows's +tiny mind, and there's clearly some sort of permission problem preventing +this user from modifying this file. +"""]] -- cgit v1.2.3