RE: Determine files that have changed between revisions

Actually, using log is a little worse because it includes all the paths
that changed in each revision. If your looking for differences in a dir
deep in the tree this would show paths across the entire repository that
your not interested in.

Also, I've noticed that log -v is kind of expensive when there are
massive changes in a single revision. Getting the log -v for any file
that was modified in the massive revision ends up taking a while. (As a
seprate note I kind of wish svn log included the "action" for a given
file in the standard log vs. having to do a log -v where I end up having
to dig through the cluter of all the other files in each revision.)

Thanks for the suggestion though! :)

Ray

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Monday, May 10, 2004 9:45 AM
To: Garrett Rooney
Cc: Ray Johnson; users@subversion.tigris.org
Subject: Re: Determine files that have changed between revisions

On Mon, 2004-05-10 at 11:39, Garrett Rooney wrote:

> $ svn log -v -q -r 24:28 http://svn/KeenDev/trunk/sample/foo
>
> The -v tells the log output to include the changed paths information,
> -q tells it to supress the actual log message.

Of course, the only problem with this output is that it hasn't been
sorted and uniq'd. But still pretty usable.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 10 19:04:54 2004