summaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorGravatar anntzer.lee@b6e099b6ef8ba8b53005ca7f0e473e825001129b <anntzerlee@web>2016-01-08 07:35:21 +0000
committerGravatar admin <admin@branchable.com>2016-01-08 07:35:21 +0000
commitc35db5ae689a3efb67d490ba33417b91e3b2b4f2 (patch)
tree4d4b3c7aa2560b0c376b74a9f3a36231a9f998b6 /doc/bugs
parentd59bf09e7ffcf9cb6b1a9ed639fb832ff1f0b170 (diff)
Added a comment
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/git_annex_cannot_get_my_files_after_clone/comment_4_d1d13d1f3366026957d572b930cafa4b._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_cannot_get_my_files_after_clone/comment_4_d1d13d1f3366026957d572b930cafa4b._comment b/doc/bugs/git_annex_cannot_get_my_files_after_clone/comment_4_d1d13d1f3366026957d572b930cafa4b._comment
new file mode 100644
index 000000000..29853c313
--- /dev/null
+++ b/doc/bugs/git_annex_cannot_get_my_files_after_clone/comment_4_d1d13d1f3366026957d572b930cafa4b._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="anntzer.lee@b6e099b6ef8ba8b53005ca7f0e473e825001129b"
+ nickname="anntzer.lee"
+ subject="comment 4"
+ date="2016-01-08T07:35:21Z"
+ content="""
+I got the same error (with the same no-output from `ssh remote /bin/true`) with a fresh install of git annex, *when I did not have write rights to the remote's .git folder*. I temporarily solved the issue by giving myself write rights to that folder, but can this be avoided?
+"""]]