Mail Archives: djgpp/2003/02/20/21:59:51
"DJ Delorie" <dj AT delorie DOT com> wrote in message
news:200302200001 DOT h1K01QP29284 AT envy DOT delorie DOT com...
>
> > Look, if you don't care then don't ask. The original post contains
> > the information.
>
> Maybe he didn't get your original post?
I suspect he didn't read it. If he couldn't read the whole thread for
technical reasons he should have taking a more cautious approach in his
reply.
>
> > But, like I said before it doesn't really matter. An alternative
> > tool works better so I'm set. Whoever maintains DJGPP can address
> > this or not. A good tool community would have been thankful for a
> > problem report like this but I guess DJGPP is different.
>
> DJGPP is maintained by a group of volunteers. Before we can do
> *anything* about a bug, we need to (1) understand it, (2) reproduce
> it, and (3) find time to work on it. If you take the feedback from
> ONE volunteer as representative of the whole group, you're going to be
> disappointed.
It was more the trend that disappointed me. Reminded me a lot of typical
engineers I work with every day. I provided a minimal source code example
(boiled down from thousands of lines) and a clear description of the
symptoms. That should have covered (1) and (2). (3) May take a long time, I
understand. Like I said elsewhere, it doesn't have to be fixed for me but I
thought I did the DJGPP group a favour by posting this. I'm regretting
already.
>
> > Second strike. Congrats.
>
> If you want your problem solved, you have to work with us for a while.
> If you're going to be nasty about it just because you're not getting a
> perfect (to you) response, you might as well go away now. We can't
> please people as picky as you are.
OK. I'll just try to answer the questions people asked and be on my way.
Just so you know, I started with a polite and informative post but it was
the folks that replied that threw down the gauntlet. I won't have people
write to me like that and pretend it doesn't matter.
Sander
- Raw text -