3 Dec 14:06
Re: [Serna] File locking/versioning with Serna -- what are others using?
From: Eliot Kimber <ekimber@...>
Subject: Re: [Serna] File locking/versioning with Serna -- what are others using?
Newsgroups: gmane.editors.serna.user
Date: 2007-12-03 13:06:22 GMT
Subject: Re: [Serna] File locking/versioning with Serna -- what are others using?
Newsgroups: gmane.editors.serna.user
Date: 2007-12-03 13:06:22 GMT
p wrote: vnbook.red-bean.com/ > > Then take it from there. I promise you that you won't regret using subversion > as a version control system. Again, it's a biased opinion - and other people > may argue that CVS would be a better way to go. I've been using subversion on > a daily basis for more than 2 years now, and have begun to love the power of > it (and accepted it's few quirks). If the choice is between CVS and Subversion there is no question: use Subversion. Subversion does everything CVS does more or less the way CVS does it and does other important things as well, such as atomic commits of multiple files, versioning of directories, and, most important for XML content, handles Unicode data correctly (CVS does not understand Unicode and can hose up non-ASCII XML data stored in CVS as ASCII). From a UI standpoint, the popular UIs for CVS are also available for Subversion (e.g., Tortoise, Eclipse's Team features, etc.). Also, because Subversion is natively HTTP based, where CVS uses private protocols, it's much easier to expose Subversion using normal HTTP and Web-based tools rather than having to do special configurations, for example, to allow CVS pserver traffic through a firewall. If you have an existing CVS repository there is a very smooth migration path from CVS to Subversion whereby you can take your CVS repository and do a one-time import to Subversion with no loss of version history. Cheers, Eliot -- -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com
RSS Feed