I've used git in a corporate environment before. It works fine. People just need to be trained in how to use it.
The major downside is that the msysgit client for Windows is kind of slow. Although I don't use Windows personally, if other people in the organization do, this could be an issue.
> 1) git allows anyone with write access to damage your history with
> 'git push -f'. While this is OK for a very-decentralized project
> like Linux, it doesn't work well for projects that have a central
> repository with hundreds of writers.
Everyone will notice pretty quickly if the history gets messed up. Then you can restore from a backup, chastise the guilty developer, and go about your merry way. Luckily, with git, every developer in the company can act as your backup.