summaryrefslogtreecommitdiff
path: root/doc/design/exporting_trees_to_special_remotes/comment_14_41e8ef74c6e62a4321d2046b2571a246._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/design/exporting_trees_to_special_remotes/comment_14_41e8ef74c6e62a4321d2046b2571a246._comment')
-rw-r--r--doc/design/exporting_trees_to_special_remotes/comment_14_41e8ef74c6e62a4321d2046b2571a246._comment17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/design/exporting_trees_to_special_remotes/comment_14_41e8ef74c6e62a4321d2046b2571a246._comment b/doc/design/exporting_trees_to_special_remotes/comment_14_41e8ef74c6e62a4321d2046b2571a246._comment
new file mode 100644
index 000000000..41cc9826b
--- /dev/null
+++ b/doc/design/exporting_trees_to_special_remotes/comment_14_41e8ef74c6e62a4321d2046b2571a246._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""re: comments on protocol"""
+ date="2017-08-15T18:18:14Z"
+ content="""
+In `TRANSFEREXPORT STORE|RETRIEVE Key File Name`, it should always
+be possible for the File to not contain spaces in its name. But it could be
+rather painful for git-annex to avoid spaces in some cases (would need to
+link or copy the annexed file content). So well spotted.
+
+Hmm, it's actually possible for a Key to contain spaces as well,
+at least with the WORM backend.
+[[external_special_remote_protocol_broken_by_key_with_spaces]]
+
+The protocol `VERSION` is picked by the special remote, it's not
+negotiated.
+"""]]