3 ms·
That doesn't give credit for 5 days of debugging. It gives credit for raising the issue, which was already done, six years prior.
by rootlocus 3y ago
That doesn't give credit for 5 days of debugging. It gives credit for raising the issue, which was already done, six years prior.
- hmottestad 3y agoBest way to get help with an issue is to post the wrong solution. I remember hearing that somewhere.
- fragmede 3y agoCunningham's Law.
- PinkRidingHood 3y agoYou could've demonstrated it by calling it the wrong name
- layer8 3y agoThe issue reported was arguably the lower-level one uncovered by the debugging. So I’d say they reported the result of their debugging.
- FireBeyond 3y ago... and their fix. ... and their results of forward regression testing. There's a lot of people expending time here trying to absolutely minimize the OP's effort and contribution. Ignoring that the maintainer literally moved one line of code (of about forty additions) and "contributed" it with himself as the author. I'd say the maintainer plagiarized OP's code.
- autoexec 3y ago> There's a lot of people expending time here trying to absolutely minimize the OP's effort and contribution. I don't really understand that either. Someone found a problem, researched it, found and tested a solution, voluntarily offered a patch, and everyone wants to pretend that it was nothing? "It was only x lines", "it was a simple/trivial patch to an obscure project", "It wasn't done in the exact way they wanted it". What is wrong with some people! It was a bug that was reported years ago but nobody took the time to fix it. This guy put in the work and delivered, which in the end is what matters.
- deleted 3y ago[deleted]