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

Case Insensitivity

From: Riesterer, Shawn \(GE Indust, GE Fanuc\) <Shawn.Riesterer_at_ge.com>
Date: 2006-08-04 18:59:34 CEST

Where I work, every once in a while a file somehow gets committed to the
repository with the same name as a file already in the repository, but a
different case. When this file is committed then with the new case, it
appears as a new file in the repository. When someone working on
Windows then does an Update, they get an error because a file with the
same name already exists.

Is it possible to add a feature (this could be an option that could be
turned off as well via the TortiseSVN settings if working in a purely
Linux environment for example) into TortiseSVN that warns the user if
they are about commit a file to the repository with the same name but
different case and asks them if they want to rename their working copy
to match case of that in the repository? Basically, I would like
TortiseSVN to handle the conflict between the case insensitivity of
Windows and the case sensitivity of the repository.

Here's an example:
* I attempt to add Test.txt to the trunk even though test.txt already
exists.
* TortiseSVN pops up a message stating that test.txt already exists in
the repository and I am trying to commit Test.txt and asks if I am sure
that I want to commit these changes and that committing these changes
will cause Windows users to not be able to get an update or do a
checkout until one of the files has been removed.

Or something to that nature.

Is this possible to add or is there a better way to handle the case
insensitivity of Windows better?

Thanks,
Shawn Riesterer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Aug 4 19:03:10 2006

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.