summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2012-12-05 17:00:21 +0000
committerGravatar admin <admin@branchable.com>2012-12-05 17:00:21 +0000
commitc1f5ed052eb9aa5473a333b5cb86efdc55c17ccc (patch)
treec8840a3ca1e881b85a967efa47eab938c3c8e256
parent3540e34025049ed4420810f21cdad6a5adc851c5 (diff)
Added a comment
-rw-r--r--doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment b/doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment
new file mode 100644
index 000000000..029373945
--- /dev/null
+++ b/doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.152.108.72"
+ subject="comment 1"
+ date="2012-12-05T17:00:21Z"
+ content="""
+To map a remote, it needs to run `git config --list` on the remote, and the remote may be a non-git-annex git remote. So mapping does a regular ssh first, and cannot use annex.ssh-options (because that would dump it into git-annex-shell). If that fails, it *does* fall back to using git-annex-shell, and will then use annex.ssh-options.
+
+So, not a bug, I believe.
+"""]]