Dmitry Potapov wrote:
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.
qmail-1.03 is one of the rare species which has two files which differ only in their case, namely INSTALL and install. The first one contains the documentation, the latter one is compiled from source. Apart from that I don't know any other affected projects.
On the other hand, most of the software developers are morons, especially in a corporate environment. The problem is you cannot refuse their work all the way, and they like to create evil twins (file names which were removed and added again), and case collisions. I could even see a lot of symlinks in a clearcase vob which poined to `..\..\..\../a/b/c'. Developer stupidity is unlimited.
Regards, -- -jul- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
