From 39a463c34a5690e3b8de302ccb4b5fded9e787ed Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 28 Feb 2020 19:15:22 +0000 Subject: [PATCH] Added a comment --- .../comment_5_e7a571699a2e564bb8364e353d9a1245._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_5_e7a571699a2e564bb8364e353d9a1245._comment 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 index 0000000000..42858484dc --- /dev/null +++ b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_5_e7a571699a2e564bb8364e353d9a1245._comment @@ -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. +"""]]