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

Re: `svn diff' progress

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2001-12-20 17:36:04 CET

Colin et al,

The sense in which cases (2) and (3) below involve the working copy is
only this: that knowing the client-side revisions of various files can
result in a more efficient (smaller) download from the server, because
the server can send *both* files to be diffed as svndiffs against
whatever's in the working copy.

Completely agree that the working copy is not formally relevant,
except as a provider of metadata and svndiff bases.

Anyway, this so-called "efficiency" may or may not be worth the
overhead; after all, in the case of two arbitrary revisions, there is
some effort to be spent merely in determining whether or not sending
the fulltexts would be more efficient anyway. :-)

-K

Colin Putney <cputney@whistler.com> writes:
> 2) Comparing a URL with a URL.
>
> In this case, the working copy should not be involved, since both
> files are remote. But the diff still has to happen in the client (to
> support plugable diff and merge tools, and to keep the processing load
> off the server) so each pair of files would have to be downloaded to a
> temporary work area before diffing. Examples:
>
> svn diff -r REV1 http://host/repos/dir/foo.c -r REV2
> http://host/repos/dir2/foo.c
> svn diff -r REV1:REV2 http://host/repos/dir/foo.c
>
> 3) Comparing different revisions of a file or directory in the working
> copy.
>
> This case is a bit tricky. The working copy doesn't supply content for
> diffing, but it *does* need to be examined to determine what files in
> the repository need to be compared. In the case of comparing
> directories, the tree below that directory in the working copy would
> have to be crawled. Examples:
>
> svn diff -r REV1:REV2 foo.c
> svn diff http://host/respos/branch/dir/ -r REV dir
>
> I'm not familar enough with the code to suggest an approach, but it
> would have to handle all three of these cases.
>
> Cheers,
>
> Colin
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

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