mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

update proposed external special remote protocol

Browse source
This commit is contained in:
Joey Hess 2017-08-28 15:34:26 -04:00
parent 792e582a60
commit ed5d8ee9ea
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 43 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/design/exporting_trees_to_special_remotes/comment_15_3fc518cee1a11b28da769c0915d33e3b._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 15"""
date="2017-08-28T19:00:10Z"
content="""
Since [[bugs/external_special_remote_protocol_broken_by_key_with_spaces]]
was fixed, the Key can't contain spaces any longer.
The File could still contain spaces, eg when exporting from a direct mode
repository where the worktree filename contains spaces.
In `RENAMEEXPORT`, both OldName and NewName could contain spaces.
"""]]

11
doc/design/exporting_trees_to_special_remotes/comment_16_29f598eda413c0d5e17536d8f9438d31._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 16"""
date="2017-08-28T19:32:06Z"
content="""
I've updated the proposed external special remote protocol to avoid the
whitespace concerns. Not wild about needing a separate EXPORT request,
which will probably get shoved into a global variable in most
implementations. But it does avoid needing to use some kind of encoding,
which would complicate implementations more, I feel.
"""]]