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

Re: Issue 730 related question about svn_ra_reporter_t interface

From: <luke_at_blanshard.us>
Date: 2003-01-27 18:42:10 CET

Please forgive me if this is an idiotic question, but can someone
explain why checkout does anything different from update? Shouldn't
checkout just create the top .svn directory and then invoke update?

I know that checkout is different from update in CVS, but then CVS has
that module thing going on. CVS modules are not present in Subversion,

cmpilato@collab.net writes:
 Or is there a better way to solve all this that I just haven't seen?

I think the correct way to handle issue 730 is to move the dav
checkout model into libsvn_client so all RA layers can benefit. In
short, this model is:

   - fetch the top-level directory's props and a list of entries.

   - in an atomic fashion, create the .svn directory for that directory,
     populating its .svn/entries directories

     *** (if we are interrupted after this step, 'svn up' will see all
         missing children and fetch them, building out subtrees and all)

Isn't this just reimplementing update?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:19:57 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.