diff options
| -rw-r--r-- | doc/forum/_illegal_control_characters_in_pairing_message__59___ignoring/comment_7_625df33e70f2f959c574d918a706648d._comment | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/_illegal_control_characters_in_pairing_message__59___ignoring/comment_7_625df33e70f2f959c574d918a706648d._comment b/doc/forum/_illegal_control_characters_in_pairing_message__59___ignoring/comment_7_625df33e70f2f959c574d918a706648d._comment index c84353436..e6303d1c4 100644 --- a/doc/forum/_illegal_control_characters_in_pairing_message__59___ignoring/comment_7_625df33e70f2f959c574d918a706648d._comment +++ b/doc/forum/_illegal_control_characters_in_pairing_message__59___ignoring/comment_7_625df33e70f2f959c574d918a706648d._comment @@ -7,7 +7,7 @@ Seems we can rule out user/hostname/directory, which probably leaves the ssh public key as the culprit, but I'm not sure. So, I changed the error message to display the problem data, -in [[!commit 5fd15677042b66be81936f081fe0a17f5960096f]]. Once you have a +in [[!commit f36adc2dbc46ec50ee7c88962de0a0d1473681eb]]. Once you have a git-annex version with that commit, if you see the problem, paste in the error message and I should be able to get to the bottom of this. """]] |