News for hackers. Stuff that matters.
Re:Jujutsu for Busy Devs by 1718627440 on Tuesday July 22, 2025 @06:13AM (#44645127)
Yes not using bisect, seams like you do all the work to record information, but then never use that information to save work?
Re:Jujutsu for Busy Devs by 0x457 on Tuesday July 22, 2025 @12:54PM (#44649913)
May 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.
Re:Jujutsu for Busy Devs by 1718627440 on Tuesday July 22, 2025 @01:08PM (#44650143)
> 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.

Re:Jujutsu for Busy Devs by 0x457 on Tuesday July 22, 2025 @04:44PM (#44652765)
> 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.

Re:Jujutsu for Busy Devs by 1718627440 on Wednesday July 23, 2025 @09:58AM (#44659303)
In addition to bugs this is also useful to pinpoint behaviour change.