Antoine <melser.anton <at> gmail.com> writes: > I suggest you forget CVS for the moment and try subversion > (http://subversion.tigris.org/), if only for the book > (http://svnbook.red-bean.com/). Subversion is a better version of CVS > and everything that could be done the same way was. The book is simply > fantastic. It takes you from complete beginner to expert, in a very > gentle way. While CVS is much more common there are still plenty of > subversion reps around. Once you are comfortable with subversion you > will be fine with CVS. There is also a section in the book which > explains the differences between the two.
Hmmmmm, The web page looks interesting, your sales_pitch is inviting, so let me see if I understand what your are saying.... I can more easily learn Subversion, and use it to check in code from a cvs respository, modify the code and send it back to a CVS repository (one that I do not control, such as ffmpeg) easier than actually employing CVS? That is, It's easier to use Subversion with an existing CVS project, than to actually use CVS? If/when I decide to use an IDE (eclipse, Anjuta....) It will have an option for Subversion style CVS capabilities? PS, I like the idea of Subversion, but, I'm not really running into too much difficulty with CVS (of coarse my experience with cvs is quite limited at this point), it's just something new to get use to using.... James -- [email protected] mailing list
