Migration from CVS to SVN: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(svn hints)
(→‎External links: online svn book)
Line 24: Line 24:
* [http://www.chiark.greenend.org.uk/~sgtatham/svn.html My Experiences With Subversion] by Simon Tatham
* [http://www.chiark.greenend.org.uk/~sgtatham/svn.html My Experiences With Subversion] by Simon Tatham
* [http://cvs2svn.tigris.org/cvs2svn.html cvs2svn tool page]  
* [http://cvs2svn.tigris.org/cvs2svn.html cvs2svn tool page]  
* Online book: [http://svnbook.red-bean.com/nightly/en/index.html Version Control with Subversion]


[[Category:Development]]
[[Category:Development]]

Revision as of 09:32, 30 May 2007

This page contains notes related to GRASS code migration (planned) from CVS to SVN.

Basic

  • The SVN command line interface is just like CVS, many tasks are identical- just change the program name from cvs to svn.


Gotchas

  • cvs2svn is known to break binary files (images) which were not imported into the CVS with the -kb flag. Luckily Glynn fixed most of these some months ago.
  • Files using keyword substitution, such as $Date$ in the description.html files, will have to have support for that enabled manually, once per file.
$ svn propset svn:keywords "Date" filename.txt
$ svn commit


Testing SVN repository

The testing SVN repository (initial stage: just cvs2svn --use-cvs --no-default-eol --force-branch=releasebranch_6_2 -s grass6svn grass6):

josef.fsv.cvut.cz

External links