Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3D78FF32.332B67FD@yahoo.com> Date: Fri, 06 Sep 2002 15:17:06 -0400 From: Earnie Boyd Reply-To: cygwin-developers AT cygwin DOT com X-Accept-Language: en MIME-Version: 1.0 To: cygwin-developers AT cygwin DOT com Subject: Re: Gee, everyone, thanks for the support References: <20020906150721 DOT GA22183 AT redhat DOT com> <1031329271 DOT 9096 DOT 49 DOT camel AT lifelesswks> <20020906163701 DOT GL21699 AT redhat DOT com> <3D78E7CA DOT 3047CDAD AT yahoo DOT com> <20020906175250 DOT GA24075 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > On Fri, Sep 06, 2002 at 01:37:14PM -0400, Earnie Boyd wrote: > >Perhaps cgf needs to check the MSDN before making changes to the > >w32api. Perhaps cgf needs a vacation. Perhaps cgf needs to check his > >blood pressure. ... > > Ah! The old "cgf needs a vacation" ploy. It's been a while. > > Submitting a patch would have been trivial. Instead you chose to deal > with this as if the cygwin code was something that other people were > responsible for. That may be appropriate for cygwin at cygwin but > it really isn't kosher here. > You choose to put blame elsewhere. The original problem began with your CVS commit. I appropriately fixed the change to w32api which just so happens to be hosted in the winsup CVS based on appropriate documentation. Now, I'm getting blamed for someone else's blunder. I only modified the w32api with the appropriate guard, because someone else incorrectly made the change which you kindly accepted, not my fault. The cygwin error was not my fault, the change to autoload.cc wasn't even documented in the winsup/ChangeLog, yet it was still accepted by you, not my fault. The discussion continued on cygwin-developers because that was where a problem with a prototype in w32api was first reported. The WINVER constant never changed, it's been 0x0400 since the first version of the w32api. The original thread pointed out a weakness in the documentation w.r.t. WINVER and _WINNT_WIN32. At what point in the above, do the problems for Cygwin belong to me? Earnie.