title: Need good reasons to move from Perforce to git - REALLY good reasons
body: <p>I work in a company with dev teams in both US and Europe. Each facility currently uses Perforce and we're planning to build new systems jointly. Being a distributed team, I'm keen that we move to git or Mercurial, but m'colleagues are wary. They like Perforce, and can't see any benefits of moving to a DVCS.</p>
  
  <p>Gotta admit I'm struggling to come up with good reasons that convince. A fast line between the 2 facilities means we can use a central Perforce repo, or clone one for each facility. </p>
  
  <p>A worry that has arisen is that there would not be one master repo: a developer would never know if the code he's just checked out is up to date - suppose someone else is updating same file?</p>
  
  <p>Yes I'm a git/Mercurial noob. Can anyone help me out with hard-to-argue-against reasons?</p>
  
  <p>Thanks!</p>