3 ms·

I think that OP had not so much a problem with the PowerPC maintainer coming up with his own solution (which is basically the same, except maybe fitting the cod

I think that OP had not so much a problem with the PowerPC maintainer coming up with his own solution (which is basically the same, except maybe fitting the coding style better), but the fact that all his efforts for finding the root cause of the bug were not recognized. The PowerPC maintainer could have send him a message like: "Thank you for the patch. Thank you for diving into this bug and finding the root cause. I will attribute your effort. I have taken the liberty to come up with a solution that better matches the coding standards. I hope you do not mind. I will submit the following patch." and I think the OP would be perfectly happy.

deleted 3y ago
[deleted]
jacquesm 3y ago
> but the fact that all his efforts for finding the root cause of the bug were not recognized. But they were! That's exactly what 'Reported-by' is for.
- underdeserver 3y ago
  Not exactly. Reported-by is for reporting the symptom; the root cause analysis is separate (and often requires much more work).
  - jacquesm 3y ago
    Some do, some don't. The chances of getting something fixed increase with the amount of prepwork that you do. I try to include as much detail as I can when reporting a bug, typically those reports get ignored so OP materially improved his chances by doing that, but root cause analysis is still covered by 'Reported-by' as far as I can see.