comment

diff --git a/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_1_e47d2cae9fa224bef2433eba4d21ec7e._comment b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_1_e47d2cae9fa224bef2433eba4d21ec7e._comment
new file mode 100644 (file)
index 0000000..ef44441
--- /dev/null
+++ b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_1_e47d2cae9fa224bef2433eba4d21ec7e._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-02-26T18:09:16Z"
+ content="""
+These strange options forcing use of unusual ssh sockets stick out.
+
+You don't indicate what kind of remote is being enabled. --debug output
+is often useful.
+
+The travis log is kind of enormous to take in, when all I want to know is
+the type of the remote, and maybe a --debug output. Grepping it seemed
+to suggest that target2 might be a regular git remote that has been fed
+into initremote, but I'm not sure?
+"""]]