diff options
| -rw-r--r-- | doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_4_109c33f4ed1230a54e410842de7779f7._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_4_109c33f4ed1230a54e410842de7779f7._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_4_109c33f4ed1230a54e410842de7779f7._comment new file mode 100644 index 000000000..7bb2d0ef0 --- /dev/null +++ b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_4_109c33f4ed1230a54e410842de7779f7._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2015-08-13T23:50:58Z" + content=""" +Thinking some more, getting the external special remote program installed +may be the real pain point here. + +I could easily add support for enableremote with readonly=yes, and have it +not use the external program at all, just hit the urls previously registered +with SETURLPRESENT. + +The git-annex branch would bloat some if a remote works this way, but if +the urls consist mostly of some fixed strings, and the key, then git should +pack those pretty efficiently. +"""]] |