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

Re: Some questions...

From: Tony Hoyle <tmh_at_nodomain.org>
Date: 2003-07-17 11:44:25 CEST

Jack Repenning wrote:
> So, for example, CVS update consists of the client sending a list of
> what it has, whereas SVN update consists of the client sending what it
> needs (unless I got that backwards, but either way the example works).
> The one list is essentially the complement of the other. So this
> intermediary would intuit "update," respond "yeah, yeah, yeah"
> endlessly, meanwhile launching an SVN update (and the standard SVN code
> would send along the list of what's needed).

Basically, yes. You'd end up caching information, since a live
translation would be overcomplex (it's probably enough to cache the

I might start by putting the bridge capability into cvsnt (since most of
the hard work is done & I know the code), then writing a standalone one
later. Proof of concept, I guess.


Received on Thu Jul 17 11:46:13 2003

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.