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

Re: Corrupt .svn directories

From: <kfogel_at_collab.net>
Date: 2005-06-02 18:34:24 CEST

Ryan Schmidt <subversion-2005@ryandesign.com> writes:
> > I've looked through the book, the FAQ, the mailing lists, and
> > Googled, and the recommended solution seems to be just to move the
> > whole working copy somewhere, check out a clean copy, and copy
> > across any changes. OK, fine, I could do this, I've got maybe 20
> > files changed across a few directories, it wouldn't take *that* long.
> >
> > But it seems to me that Subversion actually has all the information
> > it needs to recover from this situation. All I actually want to do
> > is force it to recreate all my .svn directories, without messing
> > with my changed files.

Subversion can't have all the information it needs to recover from
this -- or at least, sometimes it won't have all the information.
That's because all the information Subversion has about a working copy
resides in the .svn/ areas. If those are corrupt, then by definition
Subversion can't trust them, so it can't use that information. All it
can do is be very sensitive about detecting corruption, so that it
never mistakenly uses bad information.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 2 19:20:00 2005

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

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