AW: Case sensitvity and Windows

> > We just ran into a situation where TSVN showed one file in the “commit�
> > dialog as being new, although the file was already in the repo for a
> > long time. Not only that, the developer was able to check in that new
> > file successfully (which in turn let the SVN client on the build
> > server went crazy).
> >
> > [...]
> >
> > Note that this does not happen, when one chooses to use the “Commit�
> > dialog of the folder which contains the file. In that case, the
> > spelling is changed back behind the scenes and the file name is as
> before, therefore no changes can be commited, and no new files are
> > there to be added.

> This is by design. Only the commit dialog corrects case-renames
> automatically. But the add dialog must never do that. Otherwise
> you couldn't fix some renaming in case that already happened,
> or it wouldn't be possible to replace files in certain situations.
>
> But I guess a warning should be shown in such a case...

And maybe an option that allows to "repair" the file naming?

Ok, didn't know that.

But note that it also breaks the file history. SVN treates the files (correctly, I know) as different ones. But this is something that is just unexpected on the Windows platform, and for a purely Windows-based project. I cannot overlook the implications for other projects, of course, so I'm not really sure about that matter.

Best regards,
Jens Geyer (VSX)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-11-25 13:33:20 CET