[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: thoughts on self-hosting SVN

From: <cmpilato_at_collab.net>
Date: 2001-05-14 16:13:49 CEST

Daniel Stenberg <daniel@haxx.se> writes:

> 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)?

The short answer is yes, I have put some (tiny, insignificant) amount
of thought into this. I don't really have cycles to spare thinking
about it, so it would be wonderful if you would carry your ideas a few
steps further and begin to spec out such a system.

I'm not sure what I personally think about making such a "kit" part of
our 1.0 distribution, though. I mean, it should certainly exist for
beta testers, but I don't know how I feel about handing such a thing
to someone after we feel reasonably certain that everything is great.
Kinda makes me picture going to a new high-class restaurant with a
fresh young (yet reportedly talented) chef, and getting this great
filet mignon...that comes with a stomach pump and barf bag--just in
case, of course. :-) We don't want our product to advertise

Also, SVN is adding some new features unsupported by CVS (such as
directory removal, copies/moves, etc.). These scripts for dual
storage would of course have to run at the feature-support level
that's common to both CVS and SVN, which means our new clients will be
missing out on some the biggest reasons why SVN is the friggin' whip
(and CVS is, well, just whipped).

But hey, give it some thought. These days my concern is making sure
M2 is a legitimate name for our current state (and if not, getting us
there). M3 seems a million miles away to my mind right now.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:30 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.