delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/05/21/21:14:50

From: ian AT cygnus DOT com (Ian Lance Taylor)
Subject: Re: pathconv
21 May 1998 21:14:50 -0700 :
Message-ID: <199805220406.AAA22959.cygnus.cygwin32.developers@subrogation.cygnus.com>
References: <199805220110 DOT VAA29924 AT kramden DOT cygnus DOT com>
To: cgf AT cygnus DOT com
Cc: cygwin32-developers AT cygnus DOT com

   Date: Thu, 21 May 1998 21:10:31 -0400
   From: Christopher Faylor <cgf AT cygnus DOT com>

   I like the arguments and the functionality but I wonder if it should
   be called something with a 'cygnus' or 'cyg' in it just to differentiate
   it.  Or, we already have a poor, underutilized cygwin32 utility.  Could
   this functionality be added to that?

Overloading the cygwin utility doesn't sound quite right to me, since
that seems to be intended for debugging purposes.  However, calling
the command, say, cygpath, sounds reasonable.

Ian

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019