delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/08/07/16:59:56

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Sensitivity:
Subject: Re: Win2k and cygwin memory leak
To: "Jim Drash" <JDrash AT eesus DOT jnj DOT com>
cc: cygwin AT cygwin DOT com
From: Brian DOT Kelly AT empireblue DOT com
Date: Thu, 7 Aug 2003 16:58:36 -0400
Message-ID: <OFAB076707.BB79F906-ON85256D7B.007195C4@empirehealthcare.com>
MIME-Version: 1.0
X-WSS-ID: 132C6183409154-01-05

May I call you "Jim"? I may be clueless, but I'm not stupid. I would never
question King Faylor's ability to find
and fix, or work around a memory leak (and I even respect his decision not
to) but I would certainly question yours ....

As for the venom being spewed on this thread, all I want to say is that I
spent hundreds of hours
cobbling together work-arounds so I could get an open source automated
infrastructure working in a large
organization. Cygwin is just one piece of the puzzle - but it is a critical
indispensible piece. I consider my time
just as ( if not more ) valuable than anyone else's participating here.
These "disputed" memory leaks were for
me the biggest obsticle preventing me from achieving my ultimate objective
- which saved my company hundreds
of thousands of dollars they otherwise would have had to spend to acquire
the solution from third party vendors.

It would have been "nice" if there was an acknowledgement of this problem
(cygwin's or not) rather than attempted
character assassinations. But the value that Cygwin delivers for me and my
organization is so valuable and
irreplacible that *putting up* with the *meanness* here is small price to
pay to get the answers I frequently need.






"Jim Drash" <JDrash AT eesus DOT jnj DOT com>@cygwin.com on 08/07/2003 04:18:16 PM

Sent by:    cygwin-owner AT cygwin DOT com


To:    cygwin AT cygwin DOT com
cc:     (bcc: Brian Kelly/WTC1/Empire)

Subject:    Re: Win2k and cygwin memory leak



I will be happy to find and fix your specific memory leak.  My going rate
is $200/hour.  If that is satisfactory with you we can talk. If not, you
have the source, the compiler, the debugger, find it yourself or find
someone who will at a lower rate than mine.

Otherwise, "bugger off!"


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







"WellChoice, Inc." made the following
 annotations on 08/07/2003 05:00:58 PM
------------------------------------------------------------------------------
Attention!  This electronic message contains information that may be legally
confidential and/or privileged.  The information is intended solely for the
individual or entity named above and access by anyone else is unauthorized.
If you are not the intended recipient, any disclosure, copying, distribution,
or use of the contents of this information is prohibited and may be unlawful.
If you have received this electronic transmission in error, please reply
immediately to the sender that you have received the message in error, and
delete it. Release/Disclosure Statement


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

- Raw text -


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