Case-Sensitive commit allowed which created update error
Recently I achieved the installation of the Subversion system 1.2.3 (r15833) within my company as their primary version control system. We ran into an error whereby the system was hung up until I could sort through what had happened. The issue involved the committing of a file with an identical name and a capitalized extension. i.e.-somefile.ext -> somefile.EXT This was allowed without any notification of error. The system maintained history for the new file and the old file. Upon attempting to accomplish an update, all of my users where given an error that the file already existed elsewhere and could not complete their updates. We use universally the TortoiseSVN 1.2.4 Build 4479. The first question is why was no notification given that this was not an allowable commit? The second question is why the update halts when an error occurs. Is there no mechanism for logging the error and completing the update on the rest of the files?
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.361 / Virus Database: 267.12.5/147 - Release Date: 10/24/2005
Received on Tue Oct 25 18:36:22 2005
This is an archived mail posted to the Subversion Users