diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-09-19 12:14:51 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-09-19 12:14:51 -0400 |
| commit | 5a16df17cd10ba68c0d18a93e84db388ad7af52c (patch) | |
| tree | 848239520f1c53a21846f1a04e65f2fcff82f28d | |
| parent | eed362c9b960c22050439869c84770baa33182c7 (diff) | |
| parent | 58d354e715955febbf572487aa7898d2167d0560 (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
4 files changed, 36 insertions, 0 deletions
diff --git a/doc/bugs/Upload_to_S3_fails_/comment_3_cd1e768fe1e67daf08b5afd460620922._comment b/doc/bugs/Upload_to_S3_fails_/comment_3_cd1e768fe1e67daf08b5afd460620922._comment new file mode 100644 index 000000000..5efb78685 --- /dev/null +++ b/doc/bugs/Upload_to_S3_fails_/comment_3_cd1e768fe1e67daf08b5afd460620922._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="annexuser" + ip="71.198.212.13" + subject="comment 3" + date="2014-09-19T04:43:42Z" + content=""" +Was the version I listed above not using the new chunking from the `s3-aws` branch? How do I determine if my version of git-annex was built with the new or old chunking? +"""]] diff --git a/doc/forum/big_overhead/comment_13_1c8cc992f04fc63179094c494bd25025._comment b/doc/forum/big_overhead/comment_13_1c8cc992f04fc63179094c494bd25025._comment new file mode 100644 index 000000000..229ef256a --- /dev/null +++ b/doc/forum/big_overhead/comment_13_1c8cc992f04fc63179094c494bd25025._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="I know what it is now" + date="2014-09-19T02:43:22Z" + content=""" +These objects are the ones written by git-remote-gcrypt when pushing to a remote. That's why the weird dates, root pseudo-commit, crazy filenames, and big gpg encrypted blobs. All countermeasures that git-remote-gcrypt uses to keep your encrypted git remote safe and not leak information about what's in it. + +So, this is a bug in git-remote-gcrypt. It needs to clean these objects up after pushing them! (Also after failed pushes.) +"""]] diff --git a/doc/forum/big_overhead/comment_14_cbfb3d557915258e72c65a4e84df77a9._comment b/doc/forum/big_overhead/comment_14_cbfb3d557915258e72c65a4e84df77a9._comment new file mode 100644 index 000000000..87632c909 --- /dev/null +++ b/doc/forum/big_overhead/comment_14_cbfb3d557915258e72c65a4e84df77a9._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 14" + date="2014-09-19T02:59:36Z" + content=""" +<https://github.com/bluss/git-remote-gcrypt/issues/16> +"""]] diff --git a/doc/forum/big_overhead/comment_15_b973529bae549bcbaaae792f0403989b._comment b/doc/forum/big_overhead/comment_15_b973529bae549bcbaaae792f0403989b._comment new file mode 100644 index 000000000..a875cc34e --- /dev/null +++ b/doc/forum/big_overhead/comment_15_b973529bae549bcbaaae792f0403989b._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="rasmus" + ip="217.130.110.20" + subject="comment 15" + date="2014-09-19T06:29:58Z" + content=""" +Brilliant! Thanks for taking time to analyze the issue and taking the bug to `gcrypt`. + +[I'm surprised that a different key than my git-annex key is used and that it's a symmetric key, but I will explore the technology on my own]. +"""]] |