undefined | Better HN

0 pointskawsper12y ago0 comments

This one too: https://sourceware.org/bugzilla/show_bug.cgi?id=4980

0 comments

11 comments · 1 top-level

vezzy-fnord12y ago· 10 in thread

And yet none of these hold a candle to this masterpiece: https://sourceware.org/bugzilla/show_bug.cgi?id=12701

I dare you to top that.

haberman12y ago

These are so fantastic, keep them coming!

I'm a little bit proud that I one time he told me "That's a good catch" (after verbally abusing someone else previously on the same bug).

https://sourceware.org/bugzilla/show_bug.cgi?id=386

diegocg12y ago

I like this one, just because it's so stupid https://www.sourceware.org/bugzilla/show_bug.cgi?id=3266

rodgerd12y ago

I wish I could find his rant about his refusal to add binary coded decimals to the C standard, his refusal to allow anyone to add them to glibc, and his assertion that BCD is useless.

Alas, it appears un-googlable.

tptacek12y ago

Wow. I was feeling squeamish about the Ulrich Drepper pile-on in this thread, but this bug report is amazing.

keithpeter12y ago

Strikes me that a certain stiffness of attitude will serve Dr Drepper well in his new job. Perhaps people need to find a place/community that fits their cognitive style?

facorreia12y ago

And, surprisingly, it still seems to be not fixed.

illumen12y ago

The reporter didn't provide enough detail to begin with, and was rude as well.

No excuse for rudeness, but I understand why he may have gotten that way.

Can you imagine the number of silly bugs the glibc maintainer has to go through? Year, after year? Especially when people don't give enough evidence.

That is bug twelve thousand seven hundred and one. Developing a way to deal with all of those badly reported bugs quickly would be to do it like this. Just tell the people they are wrong, and have them provide more detail to prove their case. If you say, "Can you please provide more information", often bug reports just sit there.

Again, I don't condone the behaviour personally, since I would put people above the software. But I can see how maintaining glibc for many years would warp a person.

tptacek12y ago

Not enough detail? scanf(3) returned that 2 matches were made for "0xz" against "%x%c".

If anything, I think the problem is that he provided too much detail, since that detail alone should have been dispositive.

DanBC12y ago

I am not sure why you've been so heavily downvoted, other than "lots of people disagree".

Perhaps if bug-lists are so awful to read (and I have no doubt that they are) then the people reading them need more [close] buttons.

[close - no ref to standard]; [close - no test example code]; etc, and these provide templated replies that ask people for correct reports.

"We closed this bug. You MUST provide a clear reference to the specification showing how $THING is non-compliant.

AND

you MUST provide a test example code snippet".

This would help de-stress people reading the bugs, and might prompt people providing bugs to provide correct information.

I agree that templates are often hateful nasty things - templates on Wikipedia are really nasty approach. But here the alternative is, well, also pretty unpleasant for some people.

1 more reply

jsmthrowaway12y ago

> The reporter didn't provide enough detail to begin with, and was rude as well.

drepper's skill is in goading that response out of people, sometimes unconsciously, sometimes consciously. Take note of where the rudeness began before spending 143 words apologizing for and defending him.

I struggle to think what additional information could be included in this bug report, as you request, since:

    f(x) -> y    /* erroneous */
    f(x) -> z    /* correct */

...is about the most perfectly-written bug you can ask for and was enough context for drepper to understand.

1 more reply

j / k navigate · click thread line to collapse

0 comments

11 comments · 1 top-level

vezzy-fnord12y ago· 10 in thread

And yet none of these hold a candle to this masterpiece: https://sourceware.org/bugzilla/show_bug.cgi?id=12701

I dare you to top that.

haberman12y ago

These are so fantastic, keep them coming!

I'm a little bit proud that I one time he told me "That's a good catch" (after verbally abusing someone else previously on the same bug).

https://sourceware.org/bugzilla/show_bug.cgi?id=386

diegocg12y ago

I like this one, just because it's so stupid https://www.sourceware.org/bugzilla/show_bug.cgi?id=3266

rodgerd12y ago

I wish I could find his rant about his refusal to add binary coded decimals to the C standard, his refusal to allow anyone to add them to glibc, and his assertion that BCD is useless.

Alas, it appears un-googlable.

tptacek12y ago

Wow. I was feeling squeamish about the Ulrich Drepper pile-on in this thread, but this bug report is amazing.

keithpeter12y ago

Strikes me that a certain stiffness of attitude will serve Dr Drepper well in his new job. Perhaps people need to find a place/community that fits their cognitive style?

facorreia12y ago

And, surprisingly, it still seems to be not fixed.

illumen12y ago

The reporter didn't provide enough detail to begin with, and was rude as well.

No excuse for rudeness, but I understand why he may have gotten that way.

Can you imagine the number of silly bugs the glibc maintainer has to go through? Year, after year? Especially when people don't give enough evidence.

Again, I don't condone the behaviour personally, since I would put people above the software. But I can see how maintaining glibc for many years would warp a person.

tptacek12y ago

Not enough detail? scanf(3) returned that 2 matches were made for "0xz" against "%x%c".

If anything, I think the problem is that he provided too much detail, since that detail alone should have been dispositive.

DanBC12y ago

I am not sure why you've been so heavily downvoted, other than "lots of people disagree".

Perhaps if bug-lists are so awful to read (and I have no doubt that they are) then the people reading them need more [close] buttons.

[close - no ref to standard]; [close - no test example code]; etc, and these provide templated replies that ask people for correct reports.

"We closed this bug. You MUST provide a clear reference to the specification showing how $THING is non-compliant.

AND

you MUST provide a test example code snippet".

This would help de-stress people reading the bugs, and might prompt people providing bugs to provide correct information.

I agree that templates are often hateful nasty things - templates on Wikipedia are really nasty approach. But here the alternative is, well, also pretty unpleasant for some people.

1 more reply

jsmthrowaway12y ago

> The reporter didn't provide enough detail to begin with, and was rude as well.

I struggle to think what additional information could be included in this bug report, as you request, since:

    f(x) -> y    /* erroneous */
    f(x) -> z    /* correct */

...is about the most perfectly-written bug you can ask for and was enough context for drepper to understand.

1 more reply

j / k navigate · click thread line to collapse