Migration from CVS to SVN: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
m (→‎Testing SVN repository: rsync only grass6)
Line 19: Line 19:
Get copy of GRASS repository
Get copy of GRASS repository


  rsync -r --times --links --bwlimit=200 rsync://rsync.intevation.de/grass grass-cvs
  rsync -r --times --links --bwlimit=200 rsync://rsync.intevation.de/grass/grass6 grass6-cvs


The testing SVN repository  
The testing SVN repository  

Revision as of 15:51, 9 September 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 (or write a find routine with | xargs svn ...).
$ svn propset svn:keywords "Date" filename.txt
$ svn commit
  • how to maintain timestamps of files? We want to keep the last modification date, not the date of local download

Testing SVN repository

Get copy of GRASS repository

rsync -r --times --links --bwlimit=200 rsync://rsync.intevation.de/grass/grass6 grass6-cvs

The testing SVN repository

  • initial stage:
cvs2svn --use-cvs --no-default-eol --force-branch=releasebranch_6_2 -s grass6svn grass6
josef.fsv.cvut.cz

External links