From a8b25288a140de1a9c2c7a204ad330558453831b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 3 May 2016 13:02:11 -0400 Subject: [PATCH] response --- ...1_588af0e0b655966c2d344f3f4b4d2e5f._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/unable_to_clone_annex_repo_in_windows/comment_1_588af0e0b655966c2d344f3f4b4d2e5f._comment diff --git a/doc/forum/unable_to_clone_annex_repo_in_windows/comment_1_588af0e0b655966c2d344f3f4b4d2e5f._comment b/doc/forum/unable_to_clone_annex_repo_in_windows/comment_1_588af0e0b655966c2d344f3f4b4d2e5f._comment new file mode 100644 index 0000000000..b7ab2df61f --- /dev/null +++ b/doc/forum/unable_to_clone_annex_repo_in_windows/comment_1_588af0e0b655966c2d344f3f4b4d2e5f._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-05-03T16:55:42Z" + content=""" +That sounds like this bug: + + +Windows has some path length issues that come up especially when using +git-annex in a deeply nested directory tree. Try cloning the repository to +somewhere like c:\\ and see if that works around the problem. + +Although, the path it's complaining about is relative and only 113 +characters long, which should not be long enough to trigger that problem. +So, this could be some other problem. I tried cloning a git-annex repo +and git annex init did not fail like this, so any information you can +provide to help me reproduce the problem would be good. +"""]]