aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-05-03 13:02:11 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-05-03 13:02:11 -0400
commitb4c63ccbe624cf131810cedb6200d954cdd3bea2 (patch)
tree1f521a81123760d9b0c0d730d15ccb5df98176b8
parentc9d860e1dcf47720fc5d14347bacd1c954138b1a (diff)
response
-rw-r--r--doc/forum/unable_to_clone_annex_repo_in_windows/comment_1_588af0e0b655966c2d344f3f4b4d2e5f._comment18
1 files changed, 18 insertions, 0 deletions
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 000000000..b7ab2df61
--- /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:
+<http://git-annex.branchable.com/bugs/__34__git-annex__58___direct__58___1_failed__34___on_Windows/>
+
+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.
+"""]]