Re: Cygwin: problem with renaming and case

From: streamlake@tiscali.it <streamlake@tiscali.it>
Date: Mar 21, 2008, 19:37 UTC
Message-ID: <47E40E8C.9040805@tiscali.it>
In-Reply-To: <37fcd2780803211157n15cec620gb5ab1d3e57ccd37b@mail.gmail.com>

Dmitry Potapov ha scritto:

Show 12 quoted lines

>
>
> I wonder do you really need to have two files on different branches whose
> name only differ by case, especially when you work on case insensitive
> filesystem? I suspect the answer is no. In this case, you can choose one
> policy for file naming and stick to it. For instance, that all names should
> be in low case except Makefile, or something like that. This policy can be
> enforced using pre-commit hook.
>
> Dmitry
>
>

You're right, in fact it usually happens as the result of a mistake in naming a file between two branches or deleting a file and creating another one months later with the same name, not really a question of policies... :-)

@Linus As always, I'm absolutely not a windz fan (and this is demonstrated by the fact that I've been using cygwin for long time instead of the crappy win command prompt, and use linux every day for a few non-strictly-windz projects), but I 'must' use it if I want to work, there's no choice where I come from, and I can't change the market by myself, even if I strongly support linux as a substitute... So, given the fact that git is almost 'officially' supported at least under cygwin, I think it would be a good idea, if technically possible, to have a look at this kind of features. Not to mention the fact that having a broader audience for a project like git can be positive...

Thanks for your help, Frank