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

Re: MacOSX, and handling the loss of .svn/ from managed subdirectories

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-04-13 23:11:02 CEST

Ryan Schmidt wrote:
>
>> The only way I've found to fix this so far is to check out a second
>> copy of the project, and copy .../second/project/Main.wo/.svn to
>> .../first/project/Main.wo/.svn . I'm sure there must be a better way
>> of doing this.
>
> No, that is the way you'll have to reconstruct the .svn directories.
> Subversion does not make it easier to do this because Subversion wants
> to encourage you not to mess with the .svn directories. I realize you
> didn't do so intentionally or even directly, but Subversion
> unfortunately doesn't see those distinctions.

Has anyone tried this the other way around? Perhaps by checking out a
new copy, then using rsync -Cav to copy your modified files on top of
the new checkout, ignoring the .svn directories and contents?

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 13 23:11:16 2007

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