On Tue, Jun 1, 2010 at 19:12, Bill Dugan <bdugan_at_torpexgames.com> wrote:
> Bug summary: Our repository, hosted by wush.net, had these files (among
> others!) in it:
> The result was that on one of our Windows 7 machines, the latest TortoiseSVN
> GUI gave incomprehensible error messages to us when updating, until at last
> we detected the issue, renamed the older two files in the repository so the
> filenames didn’t conflict, deleted the entire local directory, and updated.
> Unfortunately this took us six hours to determine and fix the problem today.
> Desired behavior: Alert us when conflicting filenames (meaning, differing
> only in case) are present in the repository, and name the files, so we can
> go rename some of the files in the repository. From a design standpoint I’d
> like this to occur every time the client updates, but I’m ignorant as to
> whether this would cripple performance. If it does cripple performance,
> maybe the dialog box that occurs upon a “Clean Up” command could have a
> button you could press to have TortoiseSVN go and scan the repository for
> conflicting-in-case-only filenames.
The correct solution to this is to prevent these file name collisions
from happening in the first place. Install case-insensitive.py in your
repository as a pre-commit hook script.
Subversion, like every sane filesystem, is case-sensitive. So to
Subversion, those filenames truly are different. It's only on Windows
and MacOS (when using the default HFS+ setup) that this conflict
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-06-02 04:12:40 CEST