diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-07-16 15:01:55 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-07-16 15:01:55 -0400 |
| commit | a63e44eef44d7a0c424b8ddf0a7d0a8832a313f6 (patch) | |
| tree | 7230de298d43bdaac2908c2d0434a55e3ef47bf3 /doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment | |
| parent | 1396113ccbb6be895b1deb7c7eec228323e47078 (diff) | |
move forum bug report to bugs, and close
Diffstat (limited to 'doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment')
| -rw-r--r-- | doc/bugs/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/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment b/doc/bugs/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/bugs/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) +"""]] |