With svn, a clever attacker can make changes to past commits in the repository, so you will not see new commits to review, your own copy of the code will not co

With svn, a clever attacker can make changes to past commits in the repository, so you will not see new commits to review, your own copy of the code will not contain the changes, but when a fresh copy is checked out by eg, a build server for deployment, it will get the modified code. Git mostly prevents that; while sha1 can be attacked, a new, visible commit would have to be made containing the sha1 preimage.