Edward Ned Harvey wrote:
> I haven’t been able to reproduce any bad behavior using svn command
> line, so I think it’s a Tortoise thing, and am reporting it here first.
> Please let me know if there’s a procedure I should follow, or someplace
> else I should go instead. Thank you.
> I captured screen shots and put them here. This is the best place to
> see what I’m reporting:
> For anyone who would prefer reading –
> · At some point in history (about a year ago) we had a mac user
> commit files with ‘foo (x|y) bar’ in the filename.
> · This caused problems back then for windows users, so the files
> were renamed to exclude the parens and vertical bar. Via svn mv
The parens are not a problem, only the bar is.
> · In Tortoise now, if we do a sparse checkout (immediates) of
> the parent, and then try to go fully recursive (infinity) on the subdir
> which contains the formerly renamed files … Then Tortoise chokes while
> showing the filename which has not existed for over a year.
> · Using tortoise, if we do a fully recursive checkout of
> **just** the subdir containing the formerly renamed files, there is no
Can you please try with the Subversion command line client?
$ svn update --depth infinity --set-depth infinity path/to/workingcopy
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-01-30 21:06:17 CET