|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Windows, file names are not case sensitive. Hence, lots of existing native projects don't care about correct case. Hence, it is a real hack to find find out the actual case that one have to type in as the source. In 75% of all cases yesterday I had case-typos due to the simply silly case used by the original windows-native build scripts (which I neither own now may change). And more worse, some windows-native build tools simply turn case upper or lower just as they like - since it plays no role on windows, and since those tools are way too old.
So if you don't want CIFS plugin to help windows users identify their typos, it would at least great if there would be a checkback saying "[X] Ignore case of source".