Jens Geyer wrote:
> Hi all,
>
>
>
> 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).
>
> The problem was caused by a slightly different spelling: Instead of
> const_Something.pas the file name was in his working copy
> Const_Something.pas, with a large “C”. Sometimes Delphi renames files
> caused by other things, but normally that is not a problem. Not so in
> this case.
>
> To reproduce, take the following steps:
> - Choose a file in your working copy
> - Rename it to different spelling (using any suitable tool,
> except TSVN)
> - The file is now shown with a question mark
> - Right-click the file and choose “Add”
> - The file is shown in the ”Add” dialog and can be added
> without problems
> - The added file can be commited to the repo without problems
>
>
> 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...
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-11-24 18:05:01 CET