We used SourceForge.net's CVS service for years. It served us pretty well. In 2006 SourceForge made Subversion also available as service. And after short discussion WinMerge developers agreed to switch to Subversion. It fits better to our needs than CVS. So we switched from CVS to Subversion in August 2006.
They are in CVS. We did not import them to Subversion. If you need (codes of) old stable version you get them from project downloads.
Easiest way to browse our source code is through web. SourceForge.net utilizes ViewVC to access Subversion repositories via Web. WinMerge Subversion repository is available at: http://winmerge.svn.sourceforge.net/viewvc/winmerge/.
The Subversion Book is the definite guide to Subversion. Please try to find some time to look at it. There are also many Subversion and SVN resources available in the net. Just listing couple of them here:
WinMerge Subversion repository URL is:
https://winmerge.svn.sourceforge.net/svnroot/winmerge
Using above URL will checkout all branches and tags. WinMerge development happens in
trunk and URL is:
https://winmerge.svn.sourceforge.net/svnroot/winmerge/trunk
Branches are in separate folder:
https://winmerge.svn.sourceforge.net/svnroot/winmerge/branches
Current branches are:
https://winmerge.svn.sourceforge.net/svnroot/winmerge/branches/R2_6
https://winmerge.svn.sourceforge.net/svnroot/winmerge/branches/R2_8
https://winmerge.svn.sourceforge.net/svnroot/winmerge/branches/R2_10
https://winmerge.svn.sourceforge.net/svnroot/winmerge/branches/R2_12
https://winmerge.svn.sourceforge.net/svnroot/winmerge/branches/R2_14
Old branches (2.0 - 2.4 releases) are in CVS repository.
For every beta- and stable-release we add a tag. Tags are in folder:
https://winmerge.svn.sourceforge.net/svnroot/winmerge/tags
c:\devel\WinMerge\
) SVN should now checkout WinMerge trunk to given folder. Note that there is NO modules in SVN like there
is with CVS, so all files in /trunk
in SVN repository are added to folder you just created.
Don't checkout to some common folder expecting there will be WinMerge subfolder anyway!
changes.txt
) to commit dialogPlease copy/paste revision number to patch tracker item when you apply a patch to version control. It makes it easier to track changes afterwards. That information is of course available through logs and ViewVC, but it saves some time when revision number is visible in patch item.