From 74ad8ebb0cd4c34f6b8f84d9a0bfde6b23268baf Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 18 Sep 2014 18:52:17 +0000 Subject: [PATCH] Added a comment --- ...comment_2_f33ce058c9460cf7d151e739bff0440a._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/Upload_to_S3_fails_/comment_2_f33ce058c9460cf7d151e739bff0440a._comment diff --git a/doc/bugs/Upload_to_S3_fails_/comment_2_f33ce058c9460cf7d151e739bff0440a._comment b/doc/bugs/Upload_to_S3_fails_/comment_2_f33ce058c9460cf7d151e739bff0440a._comment new file mode 100644 index 0000000000..dcf719bba7 --- /dev/null +++ b/doc/bugs/Upload_to_S3_fails_/comment_2_f33ce058c9460cf7d151e739bff0440a._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 2" + date="2014-09-18T18:52:17Z" + content=""" +If you're using the new chunking system, git-annex should support resuming the upload to S3. Next time you try to send the file, it should find the chunks that were successfully sent, and resume at the chunk where it failed. + +Supporting this even for encrypted uploads was a major benefit of the new chunking system, so I hope it works...? +"""]]