Mail Archives: cygwin-developers/2002/09/06/15:16:53
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.
- Raw text -