Bugzilla – Bug 646
Win: hg log command should be case-insensitive
Last modified: 2012-05-13 04:57:54 EDT
Hallow all! i use an hg v0.9.4 - windows installed. my ropo contain an file src\bin\Makefile when i invoke under windows cmd: hg log src\bin\makefile - one cant be diplayed due to case-sensitive naming hg log src\bin\Makefile - dislay log well IMHO under Windows/DOS (and maybe on FAT FS`es) hg should be case-insensitive for file names listen in cmdline.
Adjusting title
removing Issue593 from superseder. 593 is resolved, but that did not resolve this one here.
Case-sensitivity of Mercurial's history view is intentional, we're not going to cripple it on Windows. Marking closed.
> Case-sensitivity of Mercurial's history view is intentional, we're not going > to cripple it on Windows. Marking closed. The reverse is actually true: on Windows, having the log command be case- sensitive is crippling. The Windows file system is case-insensitive. A log command that deals with file system paths case-sensitively makes it harder to use and cripples productivity.
'log' is the categorical example of a command whose case-handling behavior we won't change. If Bob on Unix has checked in foo and Foo and Alice on Windows wants to figure out who to blame, then she's going to -need- log to be case-sensitive. So while making it case-insensitive will make some things less annoying, it will make other things IMPOSSIBLE. Not a good trade-off, and not something that we will ever change. (Another way of looking at it is that Mercurial's history constitutes a case-sensitive filesystem and log looks at that filesystem and doesn't care about what OS you're on.) Also there's the not insignificant fact that this has been how Mercurial has worked for six years and changing it would be a nasty surprise for people and tools that already know how to use it correctly. This bug is closed, do not respond to it. If you have related issues or proposals other than changing the behavior of 'log', open a new issue.
--- Bug imported by bugzilla@serpentine.com 2012-05-12 08:42 EDT --- This bug was previously known as _bug_ 646 at http://mercurial.selenic.com/bts/issue646