From 22290a5f51b83eb3828951a5580ba3d2d40b51dd Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 13 Jan 2014 18:45:34 +0000 Subject: Added a comment --- .../comment_11_8d3c35eb0a2a9c57b10566fcaf56d248._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/design/external_special_remote_protocol/comment_11_8d3c35eb0a2a9c57b10566fcaf56d248._comment diff --git a/doc/design/external_special_remote_protocol/comment_11_8d3c35eb0a2a9c57b10566fcaf56d248._comment b/doc/design/external_special_remote_protocol/comment_11_8d3c35eb0a2a9c57b10566fcaf56d248._comment new file mode 100644 index 000000000..58c337ccd --- /dev/null +++ b/doc/design/external_special_remote_protocol/comment_11_8d3c35eb0a2a9c57b10566fcaf56d248._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.43" + subject="comment 11" + date="2014-01-13T18:45:34Z" + content=""" +I've handled the cloud repo check by making external special remotes be assumed by default to be globally available via the cloud. So no need to do anything in most cases. For remotes that are only available locally, the remote can reply with \"AVAILABILITY LOCAL\" when git-annex sends an AVAILABILITY request. +"""]] -- cgit v1.2.3