3 ms·
Bisect is a wonderful feature. Git is full of tedium and frustration, bisect is not part of that.
by ykonstant 1y ago
Bisect is a wonderful feature. Git is full of tedium and frustration, bisect is not part of that.
- falconertc 1y agoBisect is a very cool feature that I used once over 5 years ago. The collection of git tools that I use often is very small. I've found that the more experienced I got with git, the less I found myself in scenarios where I needed git's more complex tools.
- theLiminator 1y agoHmm, bisect is definitely not one of those.
- 1718627440 1y agoYes not using bisect, seams like you do all the work to record information, but then never use that information to save work?
- 0x457 1y agoMay I use how often and why you use bisect? I don't remember the last time I needed bisect. Well, I also don't work in linux kernel sized repos, so there is that.
- 1718627440 1y ago> May I use Was that 'may I ask'? Not that often, but not seldom. Its useful if you have a bug, that isn't obvious where it comes from, but easily testable. Then you just write a test and let git figure out where it comes from. The test doesn't need to be automatable. I also used it for firmware that needs to be flashed and the bug effected in an LED blinking incorrectly. I still saved a lot of time.
- 0x457 1y ago> Was that 'may I ask'? Yes, can't type sometimes. I see. Maybe it's just what kinda of code and/or how I write it, usually pretty clear which abstraction isn't doing its thing. From there, it's either clear what is the bug, or git blame will reveal what changed. This has a much higher chance of succeeding if you maintain strict boundaries and isolation which isn't always possible.
- 1718627440 1y agoIn addition to bugs this is also useful to pinpoint behaviour change.
- 0x457 1y agoSorry, that meant to be a joke. Bisect is cool and easy to use, I just never use it.