diff options
author | 2017-08-15 15:45:31 -0400 | |
---|---|---|
committer | 2017-08-15 15:45:31 -0400 | |
commit | df371efd93ca01a2378d473d964924001466aea7 (patch) | |
tree | 154b5a28eb90dbb1c9474698497242fee9be44ef | |
parent | 88ca1d8d56482221ca8eee5a89867ac485645b73 (diff) |
idea
-rw-r--r-- | doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces/comment_2_ed1299a6e12acf728bfa91e60a3706e9._comment | 13 |
1 files changed, 13 insertions, 0 deletions
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. +"""]] |