diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2018-02-07 16:24:20 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2018-02-07 16:24:20 -0400 |
| commit | 6a19c1bd34b6f0260aea648abf460611e2fab698 (patch) | |
| tree | d165bd5ce2fa0ffb873c0976a48b0adadb016a2f | |
| parent | c32727fb4f5961fde7c8902cb3009ba29bce16f8 (diff) | |
devblog
| -rw-r--r-- | doc/devblog/day_484__special_remote_protocol_extensions.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
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 000000000..68140c6fe --- /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. |