[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: Ph. Marek <philipp.marek_at_bmlv.gv.at>
Date: 2005-06-03 09:41:56 CEST

On Friday 03 June 2005 08:58, Robin Pellatt wrote:
> > Subversion can't have all the information it needs to recover from
> > this -- or at least, sometimes it won't have all the information.
> Yes it does, have a look at my proposal again:
No, it doesn't.

> ...
> Correct me if I'm wrong, but as far as I'm aware the .svn directory
> contains no information about my edits, only a pristine copy of each
> file that was checked out, and information related to that, therefore
> all the information needed to do recreate these directories is in the
> repository (On further perusal of the docs, there may be other info such
> as when I've schedule a new file for addition, but I can live with
> losing that).
But there's also stored *which revision you checked out*.
This may be not necessary if you're the only developer - but as soon as two
people work together on one repository *you need to know to which revision*
your changes apply; else your changes can't be automatically merged.

It *may* be enough to do a new checkout and copy your old wc files *without
any .svn directories* over the new wc; but I'd be very cautious and use a lot
of "svn diff" to check that I won't overwrite changes done by somebody else.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 3 09:44:19 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.