comment
authorJoey Hess <joeyh@joeyh.name>
Fri, 28 Feb 2020 18:57:49 +0000 (14:57 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 28 Feb 2020 18:57:49 +0000 (14:57 -0400)
doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_4_2a15295f0a6f907d684ca5a7134619ac._comment [new file with mode: 0644]

diff --git a/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_4_2a15295f0a6f907d684ca5a7134619ac._comment b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_4_2a15295f0a6f907d684ca5a7134619ac._comment
new file mode 100644 (file)
index 0000000..e1cd709
--- /dev/null
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2020-02-28T18:44:07Z"
+ content="""
+Since this is a regular git remote, all enableremote
+does is the usual uuid probing. And that's where it hangs,
+sshing to the remote to run git-annex-shell configlist.
+
+One thing I notice is that you went to some trouble to pass 
+with -c annex-ssh-options for target1. I assume for some important reason,
+probably having to do with making ssh work in this environment.
+But this remote is target2, so it doesn't use those options when it sshes
+to it.
+"""]]