summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-04-20 16:52:16 +0000
committerGravatar admin <admin@branchable.com>2014-04-20 16:52:16 +0000
commit375393642fee58e2817038369ba099b76ac9a17b (patch)
tree1d2434d40541e36f64a038f23c6e3d84252bbd43
parent7c01390d8bca54c00d1b832070956d3707052605 (diff)
Added a comment
-rw-r--r--doc/bugs/protocol_mismatch_after_interrupt/comment_1_415de83053dc61a64cf2e301223f1916._comment11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/protocol_mismatch_after_interrupt/comment_1_415de83053dc61a64cf2e301223f1916._comment b/doc/bugs/protocol_mismatch_after_interrupt/comment_1_415de83053dc61a64cf2e301223f1916._comment
new file mode 100644
index 000000000..6247cf42e
--- /dev/null
+++ b/doc/bugs/protocol_mismatch_after_interrupt/comment_1_415de83053dc61a64cf2e301223f1916._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.191"
+ subject="comment 1"
+ date="2014-04-20T16:52:15Z"
+ content="""
+Last time rsync seemed to fail like this it was really the remote git-annex-shell failing on an encoding problem:
+[[!commit 0b12db64d834979d49ed378235b0c19b34e4a4d6]]
+
+It seems I would need to see the transfer info files you moved out of the way to say more. Or you could copy the back, reproduce the problem, find the git-annex-shell command that is being run (using --debug), and see if you can run it on the remote system and reproduce the problem there without rsync in the picture, in order to get the actual error message.
+"""]]