diff --git a/doc/bugs/problems_with_SSH_and_relative_paths/comment_11_a2a778bd1787068cc621b17dd64b31c2._comment b/doc/bugs/problems_with_SSH_and_relative_paths/comment_11_a2a778bd1787068cc621b17dd64b31c2._comment
new file mode 100644
index 0000000000..9191f400af
--- /dev/null
+++ b/doc/bugs/problems_with_SSH_and_relative_paths/comment_11_a2a778bd1787068cc621b17dd64b31c2._comment
@@ -0,0 +1,21 @@
+[[!comment format=mdwn
+ username="asakurareiko@f3d908c71c009580228b264f63f21c7274df7476"
+ nickname="asakurareiko"
+ avatar="http://cdn.libravatar.org/avatar/a865743e357add9d15081840179ce082"
+ subject="comment 11"
+ date="2021-10-06T21:10:34Z"
+ content="""
+I'm still experiencing this bug with 8.20200226. If the repo is cloned by ssh before doing `git annex init`, then the result is:
+
+```
+  Unable to parse git config from origin
+
+  Remote origin does not have git-annex installed; setting annex-ignore
+```
+
+
+Creating an empty repo and doing `git annex init` first then adding the remote and pulling in changes works fine, but this creates unrelated history on the `git-annex` branch.
+
+
+This affects ssh remotes but not local remotes.
+"""]]