diff options
| author |  digiuser <digiuser@web> | 2015-06-24 00:49:22 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-06-24 00:49:22 +0000 |
| commit | 538426a246f3068c4b2bb4958b567667943e8707 (patch) | |
| tree | 0d4878b49cd3d630099a84312c597a7a0ccb9c19 | |
| parent | 5bde4ceb2f79cf9ee03db54f7f63c0cd5f454328 (diff) | |
Added a comment: yes
| -rw-r--r-- | doc/forum/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment b/doc/forum/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment new file mode 100644 index 000000000..df12abc03 --- /dev/null +++ b/doc/forum/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="digiuser" + subject="yes" + date="2015-06-24T00:49:22Z" + content=""" +Yes, a single chunk did get transferred correctly. + +Actually, many times I've run this experiment, many chunks did get transferred correctly. I've even verified that they are in S3, but git-annex is trying to re-upload them. + +(I haven't checked their contents in S3 but the filenames are there and the sizes are there) +"""]] |