I’m a Unix citizen. I work with the modern web, but have a soft spot for the old Internet.

Check out my site.

  • 0 Posts
  • 1 Comment
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • Quite a few times, sure. git bisect is a specific case of a more general technique – binary search fault localization – which comes in handy every once in a while (you can go a long while without needing it, but when you do need it, you’ll be thankful for it). If you can’t otherwise trace where in the code something is going wrong, bisect the code: comment or remove half of it out, see if it reproduces (therefore localizing it to either the removed or the remaining half), and repeat. If you’re working with some software that’s breaking on your config after a major version bump, bisect your config. Don’t have an idea what introduced a bug into your branch? git bisect.