diff options
Diffstat (limited to 'doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_1_8e8dd79385b523502b39247135385bc4._comment')
| -rw-r--r-- | doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_1_8e8dd79385b523502b39247135385bc4._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_1_8e8dd79385b523502b39247135385bc4._comment b/doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_1_8e8dd79385b523502b39247135385bc4._comment new file mode 100644 index 000000000..631155c20 --- /dev/null +++ b/doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_1_8e8dd79385b523502b39247135385bc4._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-11-14T19:19:30Z" + content=""" +It indeed would be possible for `copy --to` to check the actual file +size when the key does not have a known size, and use that for progress. +I don't know how hard it would be. + +Note that, even if that were done, there's no guarantee that a given remote +will update progress information, and if it doesn't, --json-progress +won't result in any. So your code certianly needs to handle that case. +"""]] |