summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2018-02-06 14:05:12 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2018-02-06 14:05:12 -0400
commit6d37a7d5a4c31493857c18b7f06d80bdcd4121d5 (patch)
tree073d8e9ce13e8d4cd84a1870dd63355c1cb64605
parentcdea5752893f4ca31fa44a5a1803d59bc7017df3 (diff)
reviewed all external special remotes for change feasability
-rw-r--r--doc/design/external_special_remote_protocol.mdwn5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/design/external_special_remote_protocol.mdwn b/doc/design/external_special_remote_protocol.mdwn
index e31ee9e9b..d6808274e 100644
--- a/doc/design/external_special_remote_protocol.mdwn
+++ b/doc/design/external_special_remote_protocol.mdwn
@@ -490,4 +490,7 @@ It works like this:
PREPARE or INITREMOTE after VERSION, so this change would break them.
I mean, they shouldn't.. But a quickly/badly written one might.
Probably want to review all the linked external special remote programs
- before doing this.
+ before doing this. Update: Reviewed them all, all are ok.
+ However, datalad's datalad's customremotes/base.py reacts to an unknown
+ request by calling self.error and so seems it would crash if git-annex
+ sent PROTOCOLKEYWORDS..