cmpilato@collab.net wrote:
>
> Stephan Feder <sf@stephan-feder.de> writes:
>
> > Has anyone thought about implementing a CVS server that uses subversion
> > as backend?
>
> Heh...that'd actually be a pretty sweet academic exercise. I mean,
> think of the benefit to sysadmins: "Team, we're switching to
> Subversion for our projects -- but if you wanna be a pansy, you can
> still use your old CVS client."
Exactly.
But for this scheme to work the svn server must be somewhat restricted
(using the existing hooks?) because svn allows for operations that
cannot be mapped onto cvs (arbitrary cheap copies, etc). So, before
rethinking all that from scratch, and because the idea is so obvious
that certainly someone must have evaluated its feasibility I wanted to
ask on the list first.
What was _not_ on my mind are (and why):
1. svn client with cvs ui (instead replace the server only while leaving
all existing clients operational and allowing users to switch from cvs
client to svn client whenever they want to)
2. svn server with cvs backend (instead take advantage of svn's superior
repository)
3. cvs client with svn ui (I do not need it)
Sorry for answering others' comments in this message but so far your
reply is the only one that did not lose track of my question.
Thanks and regards,
Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 15 01:13:08 2002