Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Wed, 16 Jun 1999 14:28:06 -0400 From: Chris Faylor To: Geoffrey Noer Cc: Earnie Boyd , cygwin developers Subject: Re: cygdrive confusing (was Re: new cygwin.dll (was Re: Make problems)) Message-ID: <19990616142806.A1305@cygnus.com> References: <19990616115714 DOT 13831 DOT rocketmail AT web116 DOT yahoomail DOT com> <19990616110822 DOT B17431 AT cygnus DOT com> <19990616141852 DOT B1197 AT cygnus DOT com> <19990616112509 DOT A17478 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990616112509.A17478@cygnus.com>; from Geoffrey Noer on Wed, Jun 16, 1999 at 11:25:09AM -0700 On Wed, Jun 16, 1999 at 11:25:09AM -0700, Geoffrey Noer wrote: >On Wed, Jun 16, 1999, Chris Faylor wrote: >[...] >> I've actually changed later snapshots so that these do not show up in >> the mount table. /cygdrive is now always usable as a default prefix for >> drives even for drives that have a mount associated with them. > >OK, never mind then. :-) > >Does this bring us closer to being able to axe /// then >I hope? I'd like to but I think we should probably wait for a long time before removing it entirely. It is only recognized now. As you know, cygwin will never generate a //x path nowadays. cgf