Daniel Barkalow wrote: > support it in git. Of course, people on Windows using projects with these > filenames will probably run into problems with other tools, but at least > git will behave properly. I don't see how it would help to have core git using the Native syntax to bypass the Win32 layer's restrictions but none of the accompanying suite of tools, i.e. the dozens of various MSYS sh.exe, perl.exe, cat.exe, etc. None of those would be able to open or even delete those files with the reserved filenames. Users tend to get upset when software creates files that cannot be removed through conventional methods, e.g. Explorer is completely powerless to remove it. Cygwin shipped with a bug several years ago that unintentionally allowed to create (but not unlink) reserved filenames. Unless you knew the magical incantation of "del \\.\c:\path\to\nul" the file was immutable. Brian -- 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
