[p4] VS: Perforce vs Seapine Surround?

Barry Au-Yeung barry_au_yeung at yahoo.com
Tue Jul 25 11:15:01 PDT 2006

  I guess various tools have implemented "private branching" in different ways, tools such as AccuRev, Surround and TFS. The fundamental idea is the same, and yes, I would not say Perforce has that "dedicated" functionality. Perforce will just treat private branch has a normal branch where other tools are much better ways to deal with private branches. You just need to choose what is the best for your company's needs.

"Ivey, William" <william_ivey at bmc.com> wrote:
  > -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com]On Behalf Of Seppo Iivonen
> Hi Barry,
> During June I was doing some research on SCM tools to find 
> out which one suited our company's needs the best. I was 
> eventually happiest with Perforce but I, for example, left 
> all Unix-based and Apache-server dependent software out as 
> they didn't fit us. Anyway, I found a good comparison chart 
> of many SCM software from Relisoft's homesite (a company 
> behind Code Co-op revision control tool):
> http://www.relisoft.com/co_op/vcs_breakdown.html

Cool chart.

I do think Perforce should have gotten a full mark for "Restore
any change any time" and maybe a partial for "Private branching"
(unless they mean the ability to keep intermediate revisions
locally; Perforce certainly doesn't prevent the creation of
private branches in the repository).


perforce-user mailing list - perforce-user at perforce.com

More information about the perforce-user mailing list