thoughts on self-hosting SVN

Hi guys

I know M3 includes SVN being self-hosted, with the SVN sources within SVN
itself.

Have anyone put any thoughts on doing some kind of duplicate storage in both
CVS and SVN (like a script that takes the comments and commits in both
systems)?

It would:

a) reduce the amount of troubles for newcomers that have CVS clients
   installed locally and want to get the SVN source. Otherwise, they'll have
   to fetch a tarball/binary first, only to install a SVN client and then get
   the source to re-install the client (and possibly the server).

b) offer the reliability of CVS in case something in SVN would blow up

Possibly, (a) can be substituted by automaticly generated tarballs or
something.

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org