- svn+ssh://YOU@svn.sv.gnu.org/PROJECT - write access for project members
- svn://svn.sv.gnu.org/PROJECT - anonymous access
- http://svn.sv.gnu.org/svn/PROJECT - slow readonly access for people who can't talk their admin into allowing outgoing SVN access
vcs:/srv/svn/PROJECT- actual host location, for admins
- The SVN book at http://svnbook.red-bean.com/
- Tips at BerliOS: http://developer.berlios.de/docman/display_doc.php?docid=394&group_id=2#convert
- The documentation from Gna! (https://gna.org/svn/?group=savane, https://gna.org/cookbook/?group=admin#svn)
- CVS to SVN conversion: see CvSToSvN.
For users: please submit a support request, including the project name and the email address to send commits to.
For admins: there is a script
create the (boilerplate) post-commit hook.
SVK add a distributed layer on top of SVN. You can find an introduction and an example at SavaneSvkBranch. SVK is a Perl tool built on top of SVN, and provides, among others, distributed features. It doesn't need a custom server, it just uses the SVN one, which sounds quite good. It's darn slow.
SVK provides the -S option to GPG-sign commits. A simple direct SVK mirror could do the trick to seamlessly sign commits. However, http://svk.elixus.org/?SVKSucks says:
svk signature is appended after the commit is done. this sucks because you cannot check the signature before accepting the commit on the server side. This also sucks because it leads to complex scripting and race condition on the server side, if you verify signatures.
Links to 3rd-party utilities
- SF.net supports SVN since feb. 2006: https://sourceforge.net/docs/E09/