It's a somewhat different issue. Git can probably not be havoced by committing two colliding files (and doing so would require doing another chosen prefix atta

It's a somewhat different issue. Git can probably not be havoced by committing two colliding files (and doing so would require doing another chosen prefix attach with a git blob header). But git looses cryptographic integrity promises due to this attack (aka: you can have different source trees with different histories leading to the same top commit hash). svn never had any cryptographic integrity to begin with.