diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2012-05-08 18:22:12 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-05-08 18:22:12 +0000 |
| commit | ac08c37649e25cd3647d3ca97bda91ffc9232889 (patch) | |
| tree | 6fbd11c076b144ccbfc94076a80de3f5dda88c7b | |
| parent | 3770bc5d4181e230159b493a2f6bef7a2f19a7b7 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Making_git-annex_less_necessary/comment_1_03faaa3866778d24cd03887b85dc9954._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/Making_git-annex_less_necessary/comment_1_03faaa3866778d24cd03887b85dc9954._comment b/doc/forum/Making_git-annex_less_necessary/comment_1_03faaa3866778d24cd03887b85dc9954._comment new file mode 100644 index 000000000..3396643f6 --- /dev/null +++ b/doc/forum/Making_git-annex_less_necessary/comment_1_03faaa3866778d24cd03887b85dc9954._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.2.245" + subject="comment 1" + date="2012-05-08T18:22:12Z" + content=""" +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.) +"""]] |