From ca48be90291bb31c696c9643e50500389e444af7 Mon Sep 17 00:00:00 2001
From: "https://tribut.de/" <Felix@web>
Date: Wed, 7 Mar 2018 20:02:07 +0000
Subject: Added a comment

---
 .../comment_2_888d17279dc33de32d7433f1f88e94e1._comment     | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_2_888d17279dc33de32d7433f1f88e94e1._comment

diff --git a/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_2_888d17279dc33de32d7433f1f88e94e1._comment b/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_2_888d17279dc33de32d7433f1f88e94e1._comment
new file mode 100644
index 000000000..ba7b1fded
--- /dev/null
+++ b/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_2_888d17279dc33de32d7433f1f88e94e1._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="https://tribut.de/"
+ nickname="Felix"
+ avatar="http://cdn.libravatar.org/avatar/d7508a030fd9902a76b02f7feff1327e80400a1317ee98e463c68ef4c9c40bb8"
+ subject="comment 2"
+ date="2018-03-07T20:02:07Z"
+ content="""
+OK, sorry for making this weird bug report then. I was getting errors like
+
+    rrsync: SSH_ORIGINAL_COMMAND='git-annex-shell' is not rsync
+
+so I assumed that my rrsync setup was incorrect and maybe it had something to do with your [recent blog](https://git-annex.branchable.com/devblog/day_486__time_to_ditch_rsync/). Unfortunately I cannot reproduce it right now, so I guess I'll wait until it happens again.
+"""]]
-- 
cgit v1.2.3


From e3f855e8e0401ecf966631d565e234fd61a6d765 Mon Sep 17 00:00:00 2001
From: "https://tribut.de/" <Felix@web>
Date: Wed, 7 Mar 2018 20:15:00 +0000
Subject: Added a comment

---
 ...ent_3_56eeb148889bc95a464f00208775aae1._comment | 34 ++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_3_56eeb148889bc95a464f00208775aae1._comment

diff --git a/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_3_56eeb148889bc95a464f00208775aae1._comment b/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_3_56eeb148889bc95a464f00208775aae1._comment
new file mode 100644
index 000000000..10ed73864
--- /dev/null
+++ b/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_3_56eeb148889bc95a464f00208775aae1._comment
@@ -0,0 +1,34 @@
+[[!comment format=mdwn
+ username="https://tribut.de/"
+ nickname="Felix"
+ avatar="http://cdn.libravatar.org/avatar/d7508a030fd9902a76b02f7feff1327e80400a1317ee98e463c68ef4c9c40bb8"
+ subject="comment 3"
+ date="2018-03-07T20:15:00Z"
+ content="""
+Got it to happen at least (though I do not believe this is was caused me to investigate this)...
+
+This works:
+
+    ± git annex sync --content
+    commit 
+    On branch master
+    Your branch is up to date with 'origin/master'.
+    
+    nothing to commit, working tree clean
+    ok
+    pull origin 
+    ok
+
+This gives the error:
+
+    ± git annex sync -J4 --content
+    /usr/local/bin/rrsync: SSH_ORIGINAL_COMMAND='git-annex-shell inannex .' is not rsync
+    
+      Unable to run git-annex-shell on remote .
+    On branch master
+    Your branch is up to date with 'origin/master'.
+    
+    nothing to commit, working tree clean
+    commit ok
+    pull origin ok
+"""]]
-- 
cgit v1.2.3