Re: svn commit: r12136 - trunk/subversion/libsvn_client
"C. Michael Pilato" <[email protected]> 03 Dec 2004 09:10:21 -0600
| Newsgroups | gmane.mail.eyebrowse.devel,gmane.comp.version-control.subversion.svn |
|---|---|
| Message-ID | <m33bynh0yq.fsf__46733.1618340269$1102086918$gmane$org@localhost.localdomain> |
Philip Martin <philip-6ttV0fGTPV0sXMjTw6Upulpr/1R2p/[email protected]> writes: > I supose we could catch/ignore the error somewhere (libsvn_ra_dav > perhaps) if that's the only thing going wrong. I don't understand the > problem sufficiently to determine whether ignoring the error is safe. I believe it would be fine for libsvn_ra_dav to catch and ignore this error. It's just trying to write an unnecessary cache to save itself some work in future operations. Or we could go all extreme and simply turn off the resource walk for switches in 1.2. This way, the wcprop callback would never get invoked during a switch, and you shouldn't see any of these problems. This would: - fix the compatibility problem. - speed up ra-dav switches. - add a few small extra network turnarounds to the first ra-dav operation that needs a vsn-rsrc-url for each path in the tree (but afterwards it would be cached). and actually, it's not even that bad, but because any paths touched during an update would get their vsn-rsrc-urls cached at no additional cost. We could always re-enable the resource walk again in the future if we wanted to.