You will seriously miss directory versioning and the ability to reorganize your source code at will. Depending on your process, you might also miss the ability to store named attributes on your artifacts. My users also make heavy use of the graphical version tree browser, which displays merges. And then there's clearmake...
--- Forwarded mail from [EMAIL PROTECTED] We have 3 CM tools within the whole comapny. CVS, Perforce, and Clearcase. Management wants to go with 1 tool. They feel Clearcase is too expensive, and it can be. I am a Clearcase guy, but know the cost. So, Perforce seems limited, CVS seems to be able to handle all that we need. I just need to make sure that there aren't any gotcha's. >From the feedback I am getting from other CVS users is that CVS handles merges poorly. I am not here to start an arguement on which is the better CM tool. I am not closed minded to think that because I know Clearcase, that it is the best tool. I am trying to find out where we may have problems with release engineering and developers. The graphical merge tool Clearacse has saves a lot of time, and it is part of Clearcase. The cost of Clearcase is just too astronomical now and like I said CVS seems to have all that we need. I am just trying to figure out what we gain and what we lose. --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
