From e8c5db3624a98dcee9c6632f691283bb2ab4c73d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 7 Feb 2018 16:24:20 -0400 Subject: [PATCH] devblog --- .../day_484__special_remote_protocol_extensions.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/devblog/day_484__special_remote_protocol_extensions.mdwn diff --git a/doc/devblog/day_484__special_remote_protocol_extensions.mdwn b/doc/devblog/day_484__special_remote_protocol_extensions.mdwn new file mode 100644 index 0000000000..68140c6fee --- /dev/null +++ b/doc/devblog/day_484__special_remote_protocol_extensions.mdwn @@ -0,0 +1,12 @@ +The +[[external special remote protocol|design/external_special_remote_protocol]] +had extensibility built into it for messages git-annex sends, but not +for messages that the remote sends back to git-annex. To fix this +asymmetry, I've added a new EXTENSIONS to the protocol, which can be used +to find out about what new protocol extensions are supported. + +There was the possibility that adding that might break some external +special remote that hardcoded the intial protocol messages. So, I checked +all of them that I know of, and all were ok, except for older versions of +datalad, which we were able to deal with. If you have your own external +special remote implementation, now would be a good time to check it.