Message-Id: <200505022301.j42N1rpL021442@delorie.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin AT cygwin DOT com>
Subject: RE: Bespoke installations: simple elegance of setup.exe when setup.ini is absent
Date: Mon, 2 May 2005 18:03:38 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.CYG.4.58.0505021728050.4048@fordpc.vss.fsi.com>
X-IsSubscribed: yes

> -----Original Message-----
> From: Brian Ford 
> Sent: Monday, May 02, 2005 5:45 PM
> To: Gary R. Van Sickle
> Cc: cygwin AT cygwin DOT com
> Subject: RE: Bespoke installations: simple elegance of 
> setup.exe when setup.ini is absent
> 
> On Thu, 28 Apr 2005, 20:58:44 -0500 Gary R. Van Sickle wrote:
> 
> > As one of the many people responsible for setup...
> 
> On Mon, 2 May 2005, Gary R. Van Sickle wrote:
> 
> > - I am responsible for a good portion of setup's UI.  It 
> used to be a 
> > series of dialog boxes.  It is now a "Wizard"-style UI.  I did that.
> 
> I believe it was simply the choice of the word responsible 
> that cgf objected to.

Unfortunately no, Brian.  What Chris objected to was my taking him to task
over an uncalled-for rude comment he made.  His comments in this thread are,
in his mind anyway, some sort of "retribution" for that.

Yeah, I don't get it either.

-- 
Gary R. Van Sickle


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/