mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2014-09-19 12:14:51 -04:00
commit 7a68a216af
4 changed files with 36 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/Upload_to_S3_fails_/comment_3_cd1e768fe1e67daf08b5afd460620922._comment Normal file
View file

@ -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?
"""]]

10
doc/forum/big_overhead/comment_13_1c8cc992f04fc63179094c494bd25025._comment Normal file
View file

@ -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.)
"""]]

8
doc/forum/big_overhead/comment_14_cbfb3d557915258e72c65a4e84df77a9._comment Normal file
View file

@ -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>
"""]]

10
doc/forum/big_overhead/comment_15_b973529bae549bcbaaae792f0403989b._comment Normal file
View file

@ -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].
"""]]