responses, bug I noticed

4 files changed, 41 insertions, 0 deletions

diff --git a/doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces.mdwn b/doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces.mdwn
new file mode 100644
index 000000000..a5e45b108
--- /dev/null
+++ b/doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces.mdwn
@@ -0,0 +1,5 @@
+It's possible for a key to contain whitespace in its name. This breaks the
+external special remote protocol, which uses whitespace to separate the key
+parameter from subsequent parameters.
+
+I think that this only causes problems for WORM keys. --[[Joey]]
diff --git a/doc/design/exporting_trees_to_special_remotes/comment_12_1bb8d57383ca733f3a0069ff30181366._comment b/doc/design/exporting_trees_to_special_remotes/comment_12_1bb8d57383ca733f3a0069ff30181366._comment
new file mode 100644
index 000000000..a039beb5f
--- /dev/null
+++ b/doc/design/exporting_trees_to_special_remotes/comment_12_1bb8d57383ca733f3a0069ff30181366._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""re: export "each revision""""
+ date="2017-08-15T18:13:38Z"
+ content="""
+That sounds much more like a regular remote with `git annex copy --all`.
+
+This entire design is preducated on exporting a single treeish. If you want
+to make a single treeish containing all versions of every file ...
+"""]]
diff --git a/doc/design/exporting_trees_to_special_remotes/comment_13_f857e15124b70ae1abc74669f63a2d68._comment b/doc/design/exporting_trees_to_special_remotes/comment_13_f857e15124b70ae1abc74669f63a2d68._comment
new file mode 100644
index 000000000..951827d49
--- /dev/null
+++ b/doc/design/exporting_trees_to_special_remotes/comment_13_f857e15124b70ae1abc74669f63a2d68._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""re: Git History"""
+ date="2017-08-15T18:16:31Z"
+ content="""
+That is entirely out of scope. You're looking for a way to store a git
+*repository* someplace like S3. Such things exist already, and are not
+git-annex and I'm not going to replicate them as part of this feature.
+"""]]
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.
+"""]]