Re: Repo Browser folder rename and uncommitted changes

Jerry Steele wrote:
> Greetings!
>
> I am just wondering what the best way to go about a parent folder rename
> is?
>
> Background:
>
> Our repository is set up as follows:
>
> Repos/
> Group1/
> Project1/
> Branches/
> Tags/
> Trunk/
> Project2/
> Branches/
> ...
> Group2/
> Project3/
> ...
> Project4/
> ...
> Group3/
> ...
>

> We had some developers that were working on the Trunk of Project1
> with uncommitted changes in their working copies. Using the
> Repository Browser, I renamed the project folder ("Project1" to
> "ProjectX"). However, when the developers updated their working
> copies before committing their local changes, all their local changes
> were blown away. Needless to say, this was a pretty costly surprise.

Are you sure they simply updated? That should not interfere with their
local changes at all. If it did, then that's a bug (a serious one) in
the Subversion library. I can't imagine such a bug going unnoticed by
the Subversion developers.

> I think this has something to do with the move/delete method of
> renaming.
>
> If anybody has checked out code in a sub-folder, must I ensure that
> they have no uncommitted changes before renaming the parent folder? >

That shouldn't be necessary.
But if local modifications really should get lost, try switching the
working copies first to the new name of the project (new url). That will
not (definitely not, I've done that several times) lose local modifications.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org