Title: For the past few years we've been using Perforce at the company I work for.  For a number of reasons, we've been given the OK from management to switch to a free SCM system.  This is supposed to be a big opportunity to improve our process and save us money, but we're having problems finding a good replacement.<p>Our must-have features include; ability to import our perforce history, easy/trivial branching and merging (preferably the ability to use an external merge tool), large file support, ability to pass changes from one workstation to another without affecting everyone, and ability to work with multiple gigs of binary files (most are roughly 500k, some are 100+megs).  The binary files are mostly build artifacts, but for a large number of very good reasons we can't expect developers to generate them.  Each developer having their own branch would be nice, but isn't critical.<p>Our products only run and compile on Windows, so decent windows support would be nice.  We aren't exactly an MS house; our product works with the artifacts of programs that only run on Windows so it runs on Windows.  Our products are very-much closed source, so things like Github are of no use to us.<p>Distributed systems like Git are compelling for the workstation to workstation support.  Unfortunately Git chokes on our binary files (I get an out of memory error), and I'm afraid that the other DSCM projects will stagnate in favor of Git.  Centralized systems like Subversions are in line with the way we've always done business, but they lack the ability to view/review/pull changes on another workstation and branching/merging isn't as easy.<p>I'm a big fan of Git, but if it can't work with large file it won't work for us.  Subversion seems like a step backwards, but I could be wrong.  Whatever we choose, we'll be with it for a long time and use it every day.<p>So, HN; what revision control system would you suggest?
Upvote: