Added a comment
authoryarikoptic <yarikoptic@web>
Fri, 28 Feb 2020 19:15:22 +0000 (19:15 +0000)
committeradmin <admin@branchable.com>
Fri, 28 Feb 2020 19:15:22 +0000 (19:15 +0000)
doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_5_e7a571699a2e564bb8364e353d9a1245._comment [new file with mode: 0644]

diff --git a/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_5_e7a571699a2e564bb8364e353d9a1245._comment b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_5_e7a571699a2e564bb8364e353d9a1245._comment
new file mode 100644 (file)
index 0000000..4285848
--- /dev/null
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 5"
+ date="2020-02-28T19:15:21Z"
+ content="""
+yes, we establish control paths (so all of us - git, git-annex, and datalad could use them and thus not re-prompting password by each tool).
+and I also spotted that we are missing control path for target2 -- [filed an issue](https://github.com/datalad/datalad/issues/4195).  But the curious point is that it doesn't stall with older git-annex.  I will rerun on travis with the same level of logging, but older git-annex, to see may be that interaction is somehow different.
+"""]]