(This is not a cheat sheet for the proper commands for cvs, rather the ones we all actually used - I'm well aware cvs had a status command, for instance, but hardly anyone used it)

Action CVS Way
SVN Way
Check out a directory without ssh cvs co -d{server address}:/path
svn co https://you@svn.kde.org/path
svn co svn+ssh@svn.kde.org/path
Check out a directory non recursively cvs co -l kdenonbeta
svn co -N https://you@svn.kde.org/path/kdenonbeta
Check out a subdirectory directly (including creating the parent folder hierarchy) cvs co kdenonbeta/morepath/somedir
mkdir -p kdenonbeta/morepath
svn co https://you@svn.kde.org/path/kdenonbeta/morepath/somedir
Commit your changes, with a message, for a set of specific files cvs ci -m "Message" file file file
svn ci -m "Message" file file file
Commit your changes, with a message, for the whole current directory and all subdirectories cvs ci -m "Message"
svn ci -m "Message"
Change to a branch for a specific subdirectory cd dir/subdir; cvs up -rBRANCH_NAME
cd dir/subdir
svn switch https://you@svn.kde.org/home/kde/BRANCHNAME/dir/subdir
Change back to HEAD for a specific directory cd dir/subdir
cvs up -A
cd dir/subdir
svn switch https://you@svn.kde.org/home/kde/trunk/KDE/dir/subdir
Use a common admin directory for KDE builds cvs co module
cvs co kde-common/admin
ln -s kde-common/admin module/admin
Using an extragear app as an example:
svn co -N svn://anonsvn.kde.org/home/kde/trunk/extragear/MODULENAME (where MODULENAME == multimedia, toys, whatever)
cd MODULENAME
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kde-common/admin
svn up APPNAME (where APPNAME == app inside module, eg, amarok in extragear/multimedia)
See if any local files have changed cd dir
cvs up
cd dir
svn status
Note: this is an offline operation (yay!)
Remove local modifications from a file, return to pristine checked out state cvs -U
svn revert
Check out a stable KDE branch cvs -rKDE_X_Y_BRANCH
TODO