diff options
author | http://joeyh.name/ <http://joeyh.name/@web> | 2014-08-03 18:27:32 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-08-03 18:27:32 +0000 |
commit | f1c574046b3f496666bed6858c11d66a17c37db2 (patch) | |
tree | 0447046bca03c20e09f5b37459cdb0327d3884e9 | |
parent | c9792f02f4554acc07adc6e3cea3aaa34ae06146 (diff) |
Added a comment
-rw-r--r-- | doc/bugs/S3_upload_not_using_multipart/comment_5_5add65b5b284f79ec09ee4d0326e7132._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_5_5add65b5b284f79ec09ee4d0326e7132._comment b/doc/bugs/S3_upload_not_using_multipart/comment_5_5add65b5b284f79ec09ee4d0326e7132._comment new file mode 100644 index 000000000..0c7742364 --- /dev/null +++ b/doc/bugs/S3_upload_not_using_multipart/comment_5_5add65b5b284f79ec09ee4d0326e7132._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.112" + subject="comment 5" + date="2014-08-03T18:27:32Z" + content=""" +However, I don't think that multipart upload actually allows exceeding the S3 limit of 5 GB per object. Configuring the remote with `chunk=100MiB` *does* allow bypassing whatever S3's maximum object size happens to be. +"""]] |