Migration from CVS to SVN: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
m (update cvs2svn command)
(svn hints)
Line 1: Line 1:
This page contains notes related to GRASS code migration (planned) from CVS to SVN.
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 ==
== Testing SVN repository ==

Revision as of 09:30, 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