From 53bee6dc5f7de3d87b39d278d558b901f243a2c9 Mon Sep 17 00:00:00 2001 From: "michael.hanke@c60e12358aa3fc6060531bdead1f530ac4d582ec" Date: Tue, 14 May 2019 08:48:27 +0000 Subject: [PATCH] Added a comment: Re: Empty lines sent by git-annex to an external special remote --- .../comment_42_485588573d8d9f74e64cdf560f65e7fe._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/design/external_special_remote_protocol/comment_42_485588573d8d9f74e64cdf560f65e7fe._comment diff --git a/doc/design/external_special_remote_protocol/comment_42_485588573d8d9f74e64cdf560f65e7fe._comment b/doc/design/external_special_remote_protocol/comment_42_485588573d8d9f74e64cdf560f65e7fe._comment new file mode 100644 index 0000000000..6250e7f427 --- /dev/null +++ b/doc/design/external_special_remote_protocol/comment_42_485588573d8d9f74e64cdf560f65e7fe._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="michael.hanke@c60e12358aa3fc6060531bdead1f530ac4d582ec" + nickname="michael.hanke" + avatar="http://cdn.libravatar.org/avatar/f881df265a423e4f24eff27c623148fd" + subject="Re: Empty lines sent by git-annex to an external special remote" + date="2019-05-14T08:48:27Z" + content=""" +Sorry for the noise. The reason was that my special remote was calling SSH internally and the parent's `stdin` was connected to the SSH process -- which confused all involved parties. +"""]]