[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: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-07-17 15:56:59 CEST

Jack Repenning <jrepenning@collab.net> writes:

> 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.

That's almost a correct analysis.

  * cvs update, as you say, sends an exhaustive list of what it has:
    every single file and it's version-number.

  * svn updates normally say "I have revision N of some big tree, with
    the following exceptions: {this subtree is a revision X, and this
    file over here is at rev Y, ...}". It's very compressed, because
    client and server have a shared understanding that "revision N" of
    some directory implies a very specific tree.

  * recently, svn updates acquired the ability to fall back into "cvs
    mode". The svn client can now say, "I have revision N of a
    directory, but I think it's incomplete, so here's an exhaustive
    list of the immediate children."

This last mode is probably what the 'translator' module would use.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 17 15:59: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.