7/14    I believe there was a thread about this a couple months ago, but...
        Does anyone have recommendations / pitfall descriptions of the
        commercial source control repositories out there.  Clear Case rocks,
        but its expensive for a 10 developer shop.  It should probably have
        support for the BSDs as well as Solaris and Linux.  Has anynoe used
        perforce?  -joshk
        \_ RCS/CVS isn't enough? -sodan with no clue
           \_ One advantage of perforce over RCS is the "change list" facility.
              Changes in several files can be submitted together in one change
              list.  This lets you later trace back easily which change in
              which file goes with which changes in which other files.  Also,
              change list submission are atomic.  Either all or none of the
              files are submitted.  Say if something goes wrong in the middle
              of submitting 30 files (e.g. merge conflict, network goes down),
              all of the files will remain unchanged on the server.  -- yuen
           \_ If you're considering CVS because it's free, look into PRCS also
                It keeps track of the project versions rather than the
                versions of the source files.
        \_ My company uses perforce and the engineers love it.  -not engineer
        \_ My company uses Perforce too.  So far so good.  -- yuen
        \_ My old company uses perforce. I've just gotten my current company
           up on perforce. (Even the marketing people are using it for change
           control on marketing docs!) So far so good here as well. -- Marco
        \_ my turn to chime in and vote for perforce.  -aspo
        \_ I've gotten two of my past projects/clients to go with Perforce
           I've even convinced Mac engineers to use its command-line interface
        \_ What? All you guys above work for perforce or something??
                \_ Maybe it's just good?  It happens sometimes.
        \_ We switched from cvs to perforce where I work.  I don't see any
           advantages of perforce.  The change list feature isn't that big
           a deal since you have to check OUT the set of files in a batch
           to check them back in as a batch.  I agree someone ought to
           add something like it to cvs but it's not that big a deal.
           Cvs isn't great, perforce isn't worse, but it doesn't seem
           better either and it costs a lot.  Sourceforge (http://www.sourceforge.net
           looks interesting but I haven't tried it and it may only be
           good for distributed projects.  --phr
                \_ Perforce costs nothing if compared to ClearCase and some of
                   other tools (Continuum, PVCS). The changelist ("batch") only
                   applies to check-ins -- check outs operate on sets of files
                   where the set population is 1..N. Where Perforce clearly
                   outguns CVS is branching and merging, not to mention labels.
                   Try syncing to a label in CVS and see how long it takes.
           \_ You don't like perforce?  This must be a troll.  :-)