From 85ea76ade10398dcfe38453dc65d08b1858a1d9e Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 19 Sep 2014 02:43:22 +0000 Subject: Added a comment: I know what it is now --- .../comment_13_1c8cc992f04fc63179094c494bd25025._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/big_overhead/comment_13_1c8cc992f04fc63179094c494bd25025._comment (limited to 'doc') 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.) +"""]] -- cgit v1.2.3 From c3961d6e6116fa41e92bcf716ef0606c2e1c8cc2 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 19 Sep 2014 02:59:36 +0000 Subject: Added a comment --- .../comment_14_cbfb3d557915258e72c65a4e84df77a9._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/big_overhead/comment_14_cbfb3d557915258e72c65a4e84df77a9._comment (limited to 'doc') 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=""" + +"""]] -- cgit v1.2.3 From 7698da943afbb7ad2e2fb6a99309fb6c17a551cc Mon Sep 17 00:00:00 2001 From: annexuser Date: Fri, 19 Sep 2014 04:43:42 +0000 Subject: Added a comment --- .../comment_3_cd1e768fe1e67daf08b5afd460620922._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Upload_to_S3_fails_/comment_3_cd1e768fe1e67daf08b5afd460620922._comment (limited to 'doc') 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? +"""]] -- cgit v1.2.3 From 58d354e715955febbf572487aa7898d2167d0560 Mon Sep 17 00:00:00 2001 From: rasmus Date: Fri, 19 Sep 2014 06:29:58 +0000 Subject: Added a comment --- .../comment_15_b973529bae549bcbaaae792f0403989b._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/big_overhead/comment_15_b973529bae549bcbaaae792f0403989b._comment (limited to 'doc') 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]. +"""]] -- cgit v1.2.3