Traction on case insensitivity on windows.

[Raindog]

Alexander Belchenko wrote:
> Raindog пишет:
>> I've recently had some ridiculous problems due to  case sensitivity 
>> of bzr on windows in which i get tons of conflicts, folder 
>> moves/renames, file deletes, adds, removes, renames etc.
>>
>> Has there been any traction on resolving this in 1.3?
>
> Please, sorry me for my bad English, but what "traction" means?
> bzr 1.3 was released last week, so there is no chance to have
> any case-insensitivity support improvements till 1.4 (in best
> case).
>
> But looking at the situation around windows support closely one could
> see that there seems to be only 2 developers working on windows support:
> Mark Hammond and Alexander Belchenko.
>
> IIUC, Mark Hammond currently working on TortoiseBzr.
>
> Alexander Belchenko working on bzr in his own free time, and he has 
> very small
> amount of free time besides his regular job and his family. Currently 
> he's
> working on simple implementation of line-endings support. Because this 
> problem
> is one of 3 most wanted (other 2 is performance and nested tree support).
>
> If anybody want to help in implementing case-insensitive filesystem 
> support,
> I can help with advices and tests. If nobody want to try get stab on it,
> then I will write such code when I will have enough time and motivation.
>
> Despite the fact I'm working 90% of my time on Windows, I managed to 
> avoid
> case-insensitive problems in my work. So although case-insensitiveness 
> is REALLY
> BIG AND IMPORTANT PROBLEM, but it's not problem for my own everyday usage
> of Bazaar, and therefore it's not itch for me to scratch urgently.
>
> It means: sorry, but it'll take a while.
>
> PS: Anybody wanna send us a patch?
>
I can work around case insensitivity on my projects now that I am aware 
of the issue (and hate visual studio for raising it) but when the files 
were renamed it was a giant pain for me to resolve everything back to 
the way it should be. I could say performance and nested trees are 
important, but when performance screws up, you just have to wait a bit. 
When file renames cause every developer on your team to have to deal 
with their "moved" directories and do the rename/merge/remove jig and 
possibly lose work, it's a giant pain in the ass.