Renaming file on case-insensitive file system cause "removed" status for older filename

[Danil]

Bazaar version: 1.11
Operating system: Windows XP SP2
File system: NTFS

Proposition

Say, I have a file 'Readme.txt' in my working copy. When I rename a file, for example to 'README.TXT', 'bzr status' command will give me a status for 'Readme.txt' as 'removed' and 'README.TXT' as 'unknown'. So, I need to add 'README.TXT' as new file. But, the status of 'Readme.txt' will be 'removed' regardless of that I touch or commit all changes to working copy.

I propose to add a configuration option (this must be an option in .cfg file, instead of command line - for convenience). The option should work on case-insensitive file systems. The option must turn on/off a specific behavior:
ON - when the file changes it's name only by changes in it's letters case (upper or lower), the bzr should mark the file as 'renamed'
OFF - default behavior, as in version 1.11

[Tim Lind (timlind)]

Just to emphasize that the old file will remain in the removed list and diff through all the commits, even after removing (with --keep) the later file. How can I get to commit this old file's removal properly?

[Vincent Ladeuil (vila)]

Basically you're renaming the file and I suppose you would like its history to be retained across this rename.
   bzr mv Readme.txt README.TXT
should just do that. You're not removing that file and adding a new one.

Can you confirm it address your problem ?

[Martin Pool (mbp)]

vila, I think you're right that will work as a workaround. The thing is, on Windows this isn't necessarily really a rename, and it may sometimes happen almost accidentally. So I think an option to handle it might be reasonable.