This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.19
- From: Nick Lowe <nick dot lowe at gmail dot com>
- To: Andrey Repin <cygwin at cygwin dot com>
- Date: Fri, 7 Jun 2013 14:29:20 +0100
- Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.19
- References: <announce dot 20130605093949 dot GA3250 at calimero dot vinschen dot de> <51AF530A dot 7080306 at shaddybaddah dot name> <20130605162825 dot GC3250 at calimero dot vinschen dot de> <CADSoG1u0101m66SbQbNPfW-J4B4o66EyQey2fdrWGy_Bya+1dg at mail dot gmail dot com> <20130607114015 dot GC32420 at calimero dot vinschen dot de>
I do not think I explained myself properly, sorry: Cygwin would
previously read the
obcaseinsensitve value under Windows 2000 to emulate the case
insensitive behaviour of Windows XP and newer where obcaseinsensitive
was present in the registry.
The registry key does not represent the active state of case
sensitivity, so it is surely the wrong thing to query and show in
cygcheck as it only shows what the state is pending a reboot. Surely
it would be better now to query how the case sensitivity actually is
here and show that, and get rid of all references to
obcaseinsensitive, which is a configuration parameter and private
implementation detail of kernel?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple