1 balupton Jan 14, 2006 10:19
3 froop May 15, 2006 10:28
Any plans to move across to SVN since it seems CVS is starting to get phased out?
4 tonsilva May 19, 2006 23:18
Notification:
The new command line for b2evo now is:
cvs -z3 -d:pserver:anonymous@evocms.cvs.sourceforge.net:/cvsroot/evocms co -P b2evolution
:D
5 marcoz Jul 04, 2006 15:45
To get the new v-1-8 branch use:
cvs -z3 -d:pserver:anonymous@evocms.cvs.sourceforge.net:/cvsroot/evocms co -r v-1-8 -P b2evolution
Marco
6 balupton Jul 11, 2006 11:32
Added instructions to the wiki, this is where tutes should now go.
http://manual.b2evolution.net/CVS_version#Check_it_out
7 zooplah Dec 16, 2008 20:06
balupton wrote:
Ok i finally figured it out, download:
WinCVS (http://cvsgui.sourceforge.net/)
In my opinion, it's more convenient to just work with the command-line CVS client. After your initial login, all you have to do is type cvs up to get the latest files (or cvs ci if you have write permissions). This is especially true if your file manager has a shell (I use Midnight Commander, which is awesome, but I used to use a Windows program that allowed it, as Windows Explorer was terribly unstable).
8 zooplah Aug 04, 2011 08:05
froop wrote:
Any plans to move across to SVN since it seems CVS is starting to get phased out?
Yeah, GNU CVS is in maintenance mode, CVSNT is commercial, and OpenCVS seems like vaporware. But still, I wouldn't too much recommend SVN; it has no fault tolerance at all. In fact, CVS remains my favorite VCS, warts and all.
Note: since a few weeks the anonymous CVS at SourceForge does not get synched with the developer's.
Please see http://manual.b2evolution.net/CVS_version for a link to a nightly snapshot.
SourceForge.Net site status: http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1