aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces.mdwn')
-rw-r--r--doc/bugs/external_special_remote_protocol_broken_by_key_with_spaces.mdwn11
1 files changed, 11 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
index a5e45b108..4180678c9 100644
--- 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
@@ -3,3 +3,14 @@ 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]]
+
+> Ok, went with my last approach, rather than complicating all special
+> remotes due to this problem, we'll deprecate WORM keys with spaces in
+> their name, and provide a migratipon path.
+>
+> The error message looks like this:
+
+> > Sorry, this file cannot be stored on an external special remote because its key's name contains a space. To avoid this problem, you can run: git-annex migrate --backend=WORM
+
+> This is fixed as well as is feasible, so while that kind of sucks,
+> calling it [[done]]. --[[Joey]]