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

"update/checkout --depth" hangup fix with 1.4 servers

From: techtonik-2 <techtonik_at_gmail.com>
Date: Mon, 20 Oct 2008 07:56:31 -0700 (PDT)

When using 1.5 client with 1.4 server - the client that is commanded to fetch
a sparse wc path with --depth=immediates for example will hang until it
rereads the whole repository. This is a well-known fact -
http://subversion.tigris.org/servlets/ReadMsg?list=users&&msgNo=80927

This behavior not only wastes time, but also overuses traffic limits. I
suspect that there is even more to it - perhaps the process enters recursion
at some point, because it is strange to wait 2 hours for sparse checkout
from a local repository via https with only 2Gb of total size when checked
out with all tags.

Why the whole repository traversal is necessary? Why was it not possible to
implement a simple logic for --depth=immediates that can be illustrated as
the following pseudo-API pseudo-code?:

/* svn co https://server/svnroot/site --depth=immediates */

svn_wc = svn_co("https://server/svnroot/site", depth="empty")
entries = svn_wc.ls()
for entry in entries:
   svn_wc.up(entry.path, depth="empty")

Regards,
anatoly t.

-- 
View this message in context: http://www.nabble.com/%22update-checkout---depth%22-hangup-fix-with-1.4-servers-tp20070395p20070395.html
Sent from the Subversion Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-20 16:56:45 CEST

This is an archived mail posted to the Subversion Dev mailing list.