From df371efd93ca01a2378d473d964924001466aea7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 15 Aug 2017 15:45:31 -0400 Subject: idea --- .../comment_2_ed1299a6e12acf728bfa91e60a3706e9._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces/comment_2_ed1299a6e12acf728bfa91e60a3706e9._comment diff --git a/doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces/comment_2_ed1299a6e12acf728bfa91e60a3706e9._comment b/doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces/comment_2_ed1299a6e12acf728bfa91e60a3706e9._comment new file mode 100644 index 000000000..9ef839f1d --- /dev/null +++ b/doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces/comment_2_ed1299a6e12acf728bfa91e60a3706e9._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2017-08-15T19:40:44Z" + content=""" +git-annex could set something in the environment to let the external +special remote know that it supports version 2. Or, git-annex could +reply to "VERSION 2" with a new request to indicate it would +like to use NUL or whatever. That would not break older clients; +they'd reply with "UNSUPPORTED-REQUEST". + +Of these, the environment variable seems cleaner. +"""]] -- cgit v1.2.3