Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <80575AFA5F0DD31197CE00805F650D7602D019@wilber.adroit.com> From: "Robinow, David" To: cygwin AT cygwin DOT com Subject: RE: //c - Ouch! Date: Wed, 26 Sep 2001 11:53:00 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" > From: Keith Starsmeare [mailto:keith_starsmeare AT yahoo DOT co DOT uk] > Subject: Re: //c - Ouch! > > 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. Except that UNC paths have been recognized for a long time. > I do know that the //c provided such a useful way to describe > a local drive /c is even more useful. Use mount!!! > ... > It's just that the implications will effect a lot of users No, it will not. //c has been deprecated for a long time. Nearly all users have made the transition. [I bet my unsupported assertion is more accurate than yours.] > 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/