Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 29 Jul 2002 23:47:09 -0400
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Cron problem
Message-ID: <20020730034709.GA25474@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <3D45BCFA.10205.5BFFFC3A@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D45BCFA.10205.5BFFFC3A@localhost>
User-Agent: Mutt/1.3.23.1i

On Mon, Jul 29, 2002 at 10:08:58PM -0400, Paul Derbyshire wrote:
>What with the big directory names debate and the big ctrl-V debate it 
>seems the cron problem thread has slipped through the cracks.

It didn't slip, exactly, as much as a bunch of us, on a lark, decided to
jump up and down on it repeatedly.  We didn't notice the crack until the
thread had pretty much been completely smooshed into it.

In fact, we were jumping so hard that I'm not even sure that we didn't
create the actual crack ourselves.

Boy I hate those thread things just lying there all cocky saying "Look
at me!  You lost a button!  Now what are you going to do?  I"m just a
piece of string!  You can't hurt meeeeee!"  I'll wipe the smile off
their thready little faces.

Anyway, sometimes me and the boys get a little carried away with
threads, if you know what I mean.

I took a look at this one though.  Held it in my arms and tried to
apologize.  It whispered to me, "Tell...  Paul...  to...  set...  his
system PATH via the Control Panel->System and then reboot...  profile
files... not... read... by...  ugh!"

Don't know if this makes sense or not but I've got to go stomp on
another thread right now.  It's sneering to me about "directories
with spaces", of all things.

cgf

--
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/