Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Mon, 3 Jan 2005 15:19:03 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: check_case:adjust still an option?
In-Reply-To:	<20050103110945.GE12820@cygbert.vinschen.de>
Message-ID:	<Pine.GSO.4.61.0501031515280.2820@slinky.cs.nyu.edu>
References:	<20050102203221 DOT GB344 AT efn DOT org> <20050102213301 DOT GA552397 AT hpn5170> <20050102221844 DOT GA608 AT efn DOT org> <20050102231344 DOT GA35436409 AT hpn5170> <20050103011210 DOT GA2112 AT efn DOT org> <Pine DOT GSO DOT 4 DOT 61 DOT 0501022019400 DOT 2820 AT slinky DOT cs DOT nyu DOT edu> <20050103110945 DOT GE12820 AT cygbert DOT vinschen DOT de>
MIME-Version:	1.0

On Mon, 3 Jan 2005, Corinna Vinschen wrote:

> On Jan  2 20:21, Igor Pechtchanski wrote:
> > On Sun, 2 Jan 2005, Yitzchak Scott-Thoennes wrote:
> > > Seems kind of pointless, really.
> >
> > It is pointless.  As I understood the documentation previously, it's the
> > POSIX path that should have been adjusted.  As is, though, it's useless.
> > FWIW, I have nothing against removing the check_case:adjust logic, as long
> > as the check_case:strict one is left in-place.  Unfortunately, most of the
> > check_case logic is associated with check_case:strict.
>
> I'd rather see check_case go away entirely since it's pointless entirely.

check_case:strict isn't.  One benefit of check_case:strict is that
whenever there's something that attemtps to create an existing file with
different case (be it archive extraction, or multiple copy, or rsync, or
whatever), you will get an error message instead of silently losing your
file.  I have been burned by this multiple times before setting
check_case:strict by default in my environment.  I don't know of any other
feature of Cygwin or Windows that will guarantee the safety of your files
in that way (except, perhaps, managed mounts, which aren't up to par yet,
IMO).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

- Raw text -