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

Bug Report: file Case conflict

From: Helder <heldersepu_at_gmail.com>
Date: Sat, 9 Feb 2008 16:42:05 -0500

Hi All

I've been using tortoise now for over a year, every once in a while
we get a "conflict" because a file was committed with different case.

Here is the scenario:
 If we try to add an existing file
  TortoiseProc /command:add /path:.\TSVN\build.txt /notempfile /closeonend
 we get this
  Error: 'TSVN\build.txt' is already under version control

 but if the file case is changed
  RENAME build.txt BUILD.TXT
 and then add it
  TortoiseProc /command:add /path:.\TSVN\BUILD.TXT /notempfile /closeonend
 the file is successfully added
 at this point the file can be committed creating a CaseConflict

I was researching this issue and found this in the Change Log:
 Version 1.0.4
 - NEW: Before a commit, TSVN scans all files in the working copy
        and adjusts the case if it got changed. (Stefan)

but is not actually "Before a commit" it seems that what actually
adjust the case of the filename is the [Check for Modifications] or
the command:
 TortoiseProc /command:repostatus /path:".\TSVN"

If I'm not mistaken the function that does the adjustment is in:
bool CSVNStatusListCtrl::BuildStatistics()

I guess it will be good idea to "scan & adjust" the parent folder
before a file is added from the command line or the explorer

The problem in a nutshell:
 Files can be added with the incorrect case and then committed

Keep up the good work!

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-09 23:04:24 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.