Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com X-Apparently-From: Message-ID: <3ACC535D.59735CFC@yahoo.com> Date: Thu, 05 Apr 2001 06:13:33 -0500 From: Earnie Boyd Reply-To: Earnie Boyd X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Larry Hall (RFK Partners, Inc)" CC: "Parker, Ron" , cygwin-developers AT cygwin DOT com Subject: Re: New output from mount.exe References: <4 DOT 3 DOT 1 DOT 2 DOT 20010404180312 DOT 02131170 AT pop DOT ma DOT ultranet DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Larry Hall (RFK Partners, Inc)" wrote: > > At 04:41 PM 4/4/2001, Parker, Ron wrote: > >Outputting c:/foo could just as easily lead to the naive user inferring that > >c:/foo is a legal cygwin path. > > Just one note. c:/foo *is* a legal Cygwin path. > And that was the point of an emphasis I made in a different thread on cygwin-apps. And the point here is that since c:\foo becomes c:foo in bash then we should output c:/foo so that that is what the user becomes familiar with. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com