git is much faster than most other versioning systems, including svn
git can even be used in tandem with svn. Sometimes companies make decisions to use svn as a policy, but the developer can create and branch at their own pace and then version the final work into svn.
git uses a single .git folder at the root of a project as the repository, and doesn't pollute every folder like svn does with .svn folders. This helps for many things, for example with grep recursive searches.
git is a distributed revision control system, where each developer only needs access to their local project folder to keep working and committing changes. If they want to “push” their commits to a remote repository, they can do this when they choose, or whenever the connection becomes available.
git allows the developer to commit as they see fit, as many times as they want, with as many branches as they want. The developer can later “squash” multiple commits, remove development branches etc… and make one nice clean commit that can be pushed to the public repository. Since the commit id's are sha-1 hashes, nobody will ever know the difference on the public server when reviewing the log.
git allows multiple “remotes” which are connections to other repositories for the same project. This could be a connection to a public repository, and/or other developer's repositories. Changes from any of these remotes can be “pulled” and merged easily, as well as “pushing” local changes to a remote if allowed.
because git is stored in the .git folder in the local project directory, each developer has an entire copy of the repository. This instantly provides redundancy for failures. If a centralized svn repository suddenly becomes unavailable, all developers will lose work because of the inability to commit.
git allows commits of portions of changes, instead of just the entire file. This is actually the way git works because it tracks “content changes”, not files. You may want a DEBUG variable set for development that shouldn't be committed. git allows you to “stage” any specific change to a file.
git allows you to easily go back and change the log message of a previous commit to correct mistakes
branching and merging are much easier in git. Even with svn 1.5, you wouldn't be able to remove a branch that didn't work out without it lingering in the repository archives.