Recent comments posted to this site:

Ok. This helped me a lot. Thank you
rsync over ssh is used to transfer file contents between repositories. (You can use the -d option to see the commands git-annex runs.)
Comment by http://joeyh.name/ Thu May 10 19:17:22 2012
Sorry if I am not clear. Actually i meant to ask, if i have 2 git repositories which are not special remotes and I am transferring annexed file content between these repositories using git annex command (move or copy) then, which protocol it uses to transfer content? Is it uses git-send-pack git-recieve-pack or some other protocols.
git-annex doesn't transfer git content between git repositories. You use git for that. Well, git-annex sync can run a few git commands for you to do it.
Comment by http://joeyh.name/ Thu May 10 18:51:56 2012
Thanks, Is git annex is using same protocols as normal git to transfer content between normal git repositories?
Some other protocols such as S3 for special remotes.
Comment by http://joeyh.name/ Thu May 10 18:18:01 2012

git's code base makes lots of assumptions hardcoding the size of the hash, etc. (grep its source for magic numbers 40 and 42...) I'd like to see git get parameratised hashes. SHA1 insecurity may evenutally push it in that direction. However, when I asked the git developers about this at the Gittogether last year, there were several ideas floated that would avoid parameterisation, and a lot of good thoughts about problems parameterised hashes would cause.

Moving data into git proper would still leave the problems unique to large data of not being able to store it all on every clone. Which means a git-annex like thing is needed to track where the data resides and move it around.

(BTW, in markdown, you separate paragraphs with blank lines. Like in email.)

Comment by http://joeyh.name/ Tue May 8 18:22:12 2012
encryption=shared is now supported
Comment by http://joey.kitenet.net/ Sun Apr 29 18:04:13 2012

I got a good laugh out of it :-)

Storing the key unencrypted would make things easier.. I think at least for my use-cases I don't require another layer of protection on top of the ssh keys that provide access to the encrypted remotes themselves.

BTW re your Tweet.. I was so happy to be able to use 'c i a' in Crypto.hs. :)
Comment by http://joey.kitenet.net/ Sun Apr 29 02:41:38 2012
Comments on this page are closed.