Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <8F23E55D511AD5119A6800D0B76FDDE101A26A3F@cpex3.channelpoint.com>
From: Troy Noble <troy DOT noble AT channelpoint DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: time:ing non-cygwin apps
Date: Wed, 5 Sep 2001 10:06:45 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/)

> Did you actually READ the code?  It is easy enough to download and
> inspectable with any simple text editor.  It is not brain surgey or
> rocket science!  It's just C++ code!

> Is this what you were expecting?  :-))

> But, seriously, FWIW, everything you said was 100% correct.  You're
> impressed by the way cygwin handles exec and I'm impressed that you
> figured it out.  Thank you for the cogent explanation.

Ugh.  Boy you scared me there for a second.  I thought I was off in
the weeds again.  Wouldn't be the first time of course ;->

I think I might join the developers list (finally) and then I won't
have to bother the world with my proposed fixes.

Definitely need to fill out an assignment form as you suggest...
unless I miss my guess, it could get into a bit more than a few
lines of code.

Troy

-----Original Message-----
From: Christopher Faylor [mailto:cgf AT redhat DOT com]
Sent: Wednesday, September 05, 2001 9:43 AM
To: cygwin AT cygwin DOT com
Subject: Re: time:ing non-cygwin apps


On Wed, Sep 05, 2001 at 09:24:27AM -0600, Troy Noble wrote:
>[snip]
>I won't go into more details now... I don't want to get flamed
>too badly at this point.  I have a couple of ideas regarding how
>to overcome this issue, but want to do some more experimenting
>before I propose them to the developers or submit a patch or whatnot.
>Hopefully if any of the above is incorrect the cygwin developers
>can set me straight... since they've got much more history with this
>stuff than I do.

Sigh.  What in the WORLD are you talking about?

Did you actually READ the code?  It is easy enough to download and
inspectable with any simple text editor.  It is not brain surgey or
rocket science!  It's just C++ code!

(Is this what you were expecting?  :-))

But, seriously, FWIW, everything you said was 100% correct.  You're
impressed by the way cygwin handles exec and I'm impressed that you
figured it out.  Thank you for the cogent explanation.

I look forward to your patch.  If your patch is going to be substantial,
however, you might want to check out the contributing link at
http://cygwin.com/ .  You don't have to join cygwin-developers
if you are not interested in becoming a full-time contributor but
you might have to fill out an assignment form if your patch is more
than a few lines.

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/

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