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

Re: Changes from 1.5 to 1.6

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 11 Jun 2009 21:16:45 +0200

Branden Visser wrote:
> Thank you for your quick reply, Bob. I'm very sorry for my delay.
>
>> I am having trouble following what you are saying here. Could you perhaps give a little script of what you are doing including paths in your repo and paths you are check out to, where you are right clicking etc.
>
> I will do my best to give a simple reproducing scenario:
>
> 1. Right Click > Repo browser
> 2. Create new Folder (Folder A)
> 3. Create new Folder as a sibling of A (Folder B)
> 4. Close repo browser
> 5. Check out Folder A (From right-click menu)
> 6. Open repo browser
> 7. Copy Folder B into Folder A (B's copy is now a subdirectory of A, call that B1)
> 8. Close repo browser
> 9. Right-Click inside of Folder A (Empty on the filesystem right now), and select "Update"
>
> Folder B1 does not come down from the repository. I have to explicitly "Check Out" Folder B1 into Folder A.

Before I try all those steps:
Did you really do the copy in the repository browser? If you did it
locally instead, then you should upgrade to 1.6.2 to not run into that
issue again. And to 'fix' the issue now, use the "update to revision"
command from the TSVN submenu, then change the depth combo to "fully
recursive". That will make the update fetch the missing folder.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2361419
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2009-06-11 21:16:57 CEST

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

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