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

Re: [Subclipse-users] WC state problems

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 8 Oct 2009 09:46:04 -0400

On Thu, Oct 8, 2009 at 9:43 AM, jcompagner <jcompagner_at_gmail.com> wrote:
>> If you delete .svn folders your working copy is broken and cannot be
>> repaired other than via checkout.  In some cases, you can remove the
>> folder that is missing the .svn folder and then run svn update on a
>> parent and it will recreate it.  I think that might actually only work
>> with missing files though.
>> Subversion 1.7 is rewriting the working copy code to remove the .svn
>> folders.  This will immediately make all problems like this disappear.
>> For now, it is your responsibility to make sure you do not do things
>> that delete or alter the .svn folders.
> ahhh!
> that would fix way more problems i think like svn folder move from one to
> the other (where i just want to copy as new)
> The patch that i created also does work fine but under mac there where some
> weird locking problems..
> But if there are no more svn folders.. where is everything stored now?
> Only the root gets the info?

For 1.7, there will be a single .svn folder in the root of the working
copy. In a future version, there is a plan to allow the metadata to
live in your $HOME or anywhere. IOW, you could have a single .svn
folder for all of your working copies. This would also enable things
like sharing the pristine copies. So if you had three copies of trunk
checked out, there would only be one extra copy of the pristine files.
 And eventually, checkout would even be smart enough to not ask the
server for the files it already has.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-10-08 15:46:12 CEST

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

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