aboutsummaryrefslogtreecommitdiff
path: root/doc/design/external_special_remote_protocol
diff options
context:
space:
mode:
Diffstat (limited to 'doc/design/external_special_remote_protocol')
-rw-r--r--doc/design/external_special_remote_protocol/comment_30_7d045871f9ebbb89e3f9bbfa28e8468f._comment18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/design/external_special_remote_protocol/comment_30_7d045871f9ebbb89e3f9bbfa28e8468f._comment b/doc/design/external_special_remote_protocol/comment_30_7d045871f9ebbb89e3f9bbfa28e8468f._comment
new file mode 100644
index 000000000..4330e7f97
--- /dev/null
+++ b/doc/design/external_special_remote_protocol/comment_30_7d045871f9ebbb89e3f9bbfa28e8468f._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 30"""
+ date="2016-05-23T18:54:35Z"
+ content="""
+You can find out the size of a key by using
+`git-annex examinekey $key --format='${bytesize}\n'`
+(There's a --batch option to avoid needing to spin up
+repeated such processes.)
+
+I suppose I could add a PROGRESSPRECENT, but any version of git-annex that
+didn't support it would fail with a protocol error if a special remote
+tried to use that. So, the special remote would need to check git-annex
+version to use it.
+
+So, maybe better to get the size of the key yourself, and convert the
+percentage to bytes for PROGRESS.
+"""]]