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

Re: On VirtualPC Rename erases File

From: Kevin Grover <kevin_at_kevingrover.net>
Date: Sat, 6 Mar 2010 13:44:42 -0800

In Windows (NTFS and FAT), filenames are case _insensitive_, so
CLSObjPrjKeys.h and cLSObjPrjKeys.h represent the same file. I know that
svn had problems with renames like this (just case change) under Windows
(and Mac, and any file system which is case insensitive).

I haven't played with this in hg, so I'm not sure if there are any issues.
If you can rename in two steps:
1) CLSObjPrjKeys.h --> temp
2) temp -> cLSObjPrjKeys.h

Then there's probably an issue with the underlying file system. These types
are problems are no really a fault of hg (or any other vcs), but more just
an known limitation of the environment.

On Fri, Mar 5, 2010 at 6:30 AM, Peter Muster <restumr_at_gmail.com> wrote:

> My Source is on a Windows7 Computer
> I work with the "Windows XP Mode" virtual computer. Here I installed the
> TortoiseSVN.
> I activated the Integrationsfeatures.
> I have a file with the name CLSObjPrjKeys.h in the repository.
> My developmentenvironment renamed it to cLSObjPrjKeys.h.
> I click "Check for modifications" and the Tortoisedialogs opens.
> Tortoise trys now to rename the file cLSObjPrjKeys.h to CLSObjPrjKeys.h.
> For some reason this doesn't work and the file is erased.
> I attach a procmon-logfile of that.
> I actually don't know, if there is a problem with my computer oder Tortoise
> has a problem with the VirtualPC.
> ------------------------------------------------------
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2455462
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_tortoisesvn.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-06 22:44:45 CET

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.