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

Re: Resolution of 'svn diff' change?

From: Colin Watson <cjwatson_at_flatline.org.uk>
Date: 2003-05-19 16:56:34 CEST

On Mon, May 19, 2003 at 09:38:26AM -0500, cmpilato@collab.net wrote:
> Colin Watson <cjwatson@flatline.org.uk> writes:
> > Also, a wrapper will be much slower than letting 'svn diff' do all the
> > files at once if your connection to the server has high setup time.
> > Consider svn+ssh to a distant machine. I do this frequently with CVS,
> > and a wrapper calling 'svn diff' multiple times would be *painful*.
> Actually, it sucks with CVS because CVS's diffs require network
> access. Subversion's don't. So your net connection won't play into
> the cost of this change at all.

Hm, good point.

I stand by my claim that it's going to be hard to tell at least certain
classes of CVS users (e.g. me a year ago) that they have to write a
wrapper for what they consider a trivial use case, though. I'd
definitely "vote" for your subcommand option (2a), since that keeps
ordinary 'svn diff' use consistent whether you're comparing one, two,
three, or more files between the working copy and the repository. 'svn
compare' would have no such consistency constraints: it can only compare
two items.


Colin Watson                                  [cjwatson@flatline.org.uk]
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 19 16:58:48 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.