Home/ Questions/Q 8184785
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T01:37:27+00:00

I work in a company with dev teams in both US and Europe. Each

  • 0

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.

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.

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?

Yes I’m a git/Mercurial noob. Can anyone help me out with hard-to-argue-against reasons?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your question does not seem to be about git/mercurial so much as centralized versus distributed VCS:

    1. Distributed VCS – pros
      • multiple copies of source; if server goes down, code is available from multiple workstations
      • local copies means that updates tend to be smaller and less network-intensive
    2. Distributed VCS – cons
      • synchonizing changes; if you have a high rate of checkin and multiple staff working on same modules you need to have a very clear protocol for push/pull/merge
    3. Centralized VCS – pros
      • one place for the code – you know which repository is or should be canonical
    4. Centralized VCS – cons
      • one place for the code – server unavailability means developers are unable to branch/version for long without issues
    • 0