Re: Gee, everyone, thanks for the support

[Christopher Faylor <cgf at redhat dot com>]

On Fri, Sep 06, 2002 at 03:17:06PM -0400, Earnie Boyd wrote:
>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 am not assigning blame elsewhere.  I screwed up in a couple of places
when adapting Chris's patch.  One of my changes caused cygwin not to
load on Windows 9x.  Big screwup on my part.  When Egor Duda noticed
that he *supplied a patch* to fix my problem.

Do you see how this worked?  Chris submitted something that wasn't quite
right.  I modified it and checked it in.  My modification was wrong so
Egor noticed and fixed it.  You noticed something pedantically incorrect
and fixed it, ignoring the fact that it now breaks cygwin.  There was a
chain here but it got broken.

I was trying to figure out why you didn't just take the extra step of
fixing cygwin when you fixed w32api.  I don't understand why it wasn't
my responsibility to fix w32api since I made the incorrect checkin but
it was my responsiblity to fix cygwin so that it continued to build.  I
am certainly not saying that it wasn't my fault for adding a guard.  I
was thinking that this was just a "Oh yeah, now that you mention it, I
could have done that" type of thing on your part.  It appears that you
have a different philosophy on how this type of issue should be handled.
I guess I understand that now.

Anyway, I think we've extracted about as much as we can from this.  It's
a tempest in a teapot.  It would be inconsistent of me not to ask about
this kind of thing when I've challenged others (jik@curl.com springs to
mind) about similar issues but I guess I consider the matter closed.

cgf