X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=vB2FHon6nV8vpDxU3345kOQu7BSRxXj3IGw3X2UogkYhmAEO7+Yuf
	JfFTQhcheD8f/cLVRNE/UPsrYD+hvv+gisuyJHXQgFsqzUU619fjjW+Fzkj7znZJ
	8RDvmFukUbqPCGmOoFYyQkue6zYXySFfuodKo9hQ4cZnTeXfE5o8Cw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=1NTf58Yr4+tCDaPVZbQz4RLfm5o=; b=fGJgkfAgtPO4IaDJ2aE3vUSMa14g
	ZbWzkWPGBEDDVX9d3W71PDSKFv6mVaWwbTZGcCf6MEeRpTZW6X2lbQEIJ8+60TRD
	ZMvPHh/0K9Cyob6vFjlfzGFK1U9zBCWZfpqdwid+Oo+kyXGcMdut5VL2pqdn7mSS
	AvBeFba7hAn66zw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,TW_YG autolearn=ham version=3.3.1
Date: Fri, 7 Jun 2013 16:11:20 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.19
Message-ID: <20130607141120.GB22187@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <CADSoG1ttmDBbeW_aC2yBqHuKHuxmmLYAYeMpmJB-rSAj4nO8rA AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CADSoG1ttmDBbeW_aC2yBqHuKHuxmmLYAYeMpmJB-rSAj4nO8rA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Jun  7 14:29, Nick Lowe wrote:
> 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?

Not from my POV, no.  The registry key is what the user has to change to
get case sensitive behaviour.  We want to know if the user actually
changed it in the first place, otherwise we can point to that info in
case of a case-sensitivity related problem.  The active state may be
interesting as well, but additionally to the registry key info and, as
far as I'm concerned, it's a minor problem.

But, anyway, http://cygwin.com/acronyms/#PTC


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple