Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <000401c146a0$bf6714c0$5d754789@edinstonehaven> From: "Keith Starsmeare" To: , "Larry Hall \(RFK Partners, Inc\)" References: <4.3.1.2.20010926104927.016fb790@pop.ma.ultranet.com> Subject: Re: //c - Ouch! Date: Wed, 26 Sep 2001 16:34:33 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > The problems you state are exactly the reasons for removing this syntax > for accessing drives. It's too dangerous and problematic. As cgf was saying the other day, small incremental changes are often more acceptable in open source projects. Maybe the cygwin dll should have gone through a six month period whereby //c was broken completely and then repaired to recognise UNC paths rather than local drives. I do know that the //c provided such a useful way to describe a local drive without referring to back slashes that it has been incorporated into other Windows based products (some Analog Devices command line tools for example). It's just that the implications will effect a lot of users and the release note (http://cygwin.com/ml/cygwin-announce/2001/msg00112.html) has it mentioned as the fifth item under "User level change overview". I'm sorry to stir this up again, but I think this needs to be in big bold flashing letters! Keith -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/