> -----Original Message-----
> From: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
> Sent: maandag 20 augustus 2012 22:10
> To: Philip Martin
> Cc: Steven Lee; Markus Schaber; users_at_subversion.apache.org
> Subject: Re: AW: Corrupt .svn directory using Subversion 1.7
>
> On Mon, Aug 20, 2012 at 1:21 PM, Philip Martin
> <philip.martin_at_wandisco.com> wrote:
> > Steven Lee <stlee987_at_gmail.com> writes:
> >
> >> On Aug 19, 2012 11:45 PM, "Steven Lee" <stlee987_at_gmail.com> wrote:
> >>>
> >>> Yes, I tried "svn update --set-depth infinity" and nothing happened.
> >> Many of the files are still missing from my working copy. It does seem
> >> like that should have worked.
> >>>
> >>
> >> Just to be clear, I tried "svn update --set-depth infinity" in the
foodir
> >> directory and "svn update --set-depth infinity foodir" in foodir's
parent
> >> directory.
> >
> > The problem is that in 1.7 the operation you interrupted is not properly
> > atomic so foodir is probably still marked as depth infinity despite
> > haoving missing children.
>
> Can / should this be fixed? Should an issue be created for this?
svn update --set-depth exclude was not atomic in 1.7, but is fully atomic on
current trunk. (Fixed about one and a half month ago)
svn update --set-depth infinity is not atomic, but is fully able to recover
from problems by restarting the same operation. Until the operation is
completed on some subtree the directory is marked incomplete and this will
make the next update (after interruption) load missing children.
(This 'incomplete' behavior was implemented far before 1.0)
Bert
Received on 2012-08-21 14:44:39 CEST