Resolution of 'svn diff' change?

I just realized that I really like (and rely upon):

svn diff dir/x dir/y

meaning dir/x and dir/y relative to the repository (as cached in the wc).

AIUI, this is now going to be a fatal error. Is that correct? I'm not really
clear what the resolution was with that thread as it went off in a million
tangents. So, pardon my request for clarification.

IMHO, this is *very* useful when you have local changes that you haven't
committed and only want a partial 'diff' subset of a directory. I use it as:

svn diff dir/x dir/y | less

to review my local changes where dir/z is also modified and I don't want to
see its diff output (and ignoring it if it is present in the diff makes it too
hard to review). Am I now going to have to do:

svn diff dir/x >1
svn diff dir/y >>1
less 1

or

for i in dir/x dir/y; do svn diff $i | less; done

whereas

svn ci dir/x dir/y

would still work as expected? (Or, will commit reject the iterative case too?)
I have a hunch that the 'diff' interface should be parallel to the 'commit'
interface - that is, they should accept the same semantics. (View diff as a
dry-run of a commit.)

If the iterative case is indeed removed as I describe above, then I'm going to
seriously contemplate vetoing any change to the 'svn diff' interface that
removes the iterative case. It's going to be extremely annoying working
around this when I have lots of local mods in my working copy (which is gonna
happen more than I'd like to admit - it's a frequent occurrence in
httpd-land). Not to mention that this would be a significant regression from
CVS with no clean alternative proposed by SVN.

Sorry for the late entry into this thread, but I'm slowly trying to catch up
on this list after being away. -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 19 09:43:11 2003