On 07.06.2010 17:14, Mike Lesher wrote:
> Experienced a recent issue with Tortoise SVN when utilizing the
> drop-n-drop functionality from a Windows7 64-bit server to a Windows
> XP ((Version 2002) - Service Pack 3) via a mapped drive. After the
> entire contents of the folder were dropped into the destination drive
> and finally copied over (via Windows Explorer), one of the
> fifty-seven (57) files appears on the destination server with a
> Windows shortname, rather than the longname as appeared in SVN.
> We found a Microsoft recommended fix for eliminating shortnames from
> being created on Windows XP as a potential workaround,
> [How to Disable Automatic Short File Name Generation
> http://support.microsoft.com/kb/210638 ],
> however are curious to how fifty-six (56) of the fifty-seven (57)
> files were copied successfully using the longname file convention and
> one file remained with the shortname conventions in place.
> This is very hard to recreate, however it did occur and has happened
> more than once using this tool.
It could be a race condition when creating files on the network share.
But one thing is certain: it can't be svn or TSVN's fault since there's
only one API to create files (CreateFile()) that's used exclusively, and
that API takes care of long/short names itself.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-06-09 20:43:51 CEST