Re: svn log hanging with dav

On Wed, 20 Oct 2004, Ben Collins-Sussman wrote:

> There's no known workaround. For every revision returned by 'svn log',
> the server now needs to inspect the changed-paths in the revision and
> decide how many are readable. Based on the answer to that question,
> the server then decides how much information to send about the
> revision: whether or not it's okay to send any of {date, author,
> log-message} and how many of the changed-paths can be revealed. That's
> what the security fix is all about.

I can see how checking all of the revisions changed-paths is necessary for
svn log -v, but why is it needed in the simpler case for only a single
file's history (no -v)? Does the server send all the changed-paths for
all revisions even when -v is not specified, relying on the client to
filter out the unneeded information?

Getting back to possible workarounds: is there some way to configure the
timeout before a client gives up on a slow operation? Taking a few
minutes to run svn log is a bit inconvenient, but telling the user "sorry,
no can do" after only a minute of waiting is unacceptable.

--Ed

-- 
Ed Swierk
eswierk@cs.stanford.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org