| ▲ | aidenn0 4 days ago | |
What about finding the commit a bug was fixed in? Example use #1: Customer using a 6-year-old version of the software wants to know if upgrading to a 4-year-old version of the software will solve their problem. Example use #2: The part of code that was likely previously causing the problem has been significantly reworked; was the bugfix intentional or accidental? If the latter, is the rework prone to similar bugs? | ||
| ▲ | geon 4 days ago | parent [-] | |
https://www.reddit.com/r/talesfromtechsupport/s/K2xme9A0MQ I once bisected to find a bug in a 6 month old commit. An off-by-one error in some array processing. I fixed the bug there to confirm. But on main, the relevant code didn’t even exist any more. It had been completely refactored away. I ended up rebasing the entire 6 months worth of commits onto the bugfix, propagating the fix throughout the refactoring. Then a diff against main showed 3 lines changed in seemingly unrelated parts of the code, together triggering the bug. I would never have found them without bisect and rebase. | ||