The sound distributed version control system

#126 `git bisect` function-a-like?

Opened by cole-h on November 27, 2020
cole-h on November 27, 2020

Is there any possibility for a pijul bisect or similar subcommand in The Future? git bisect is a programmer’s best friend when they’re trying to find the cause of a bug in an unfamiliar codebase, and, as pijul grows, many users will undoubtedly encounter situations where a pijul bisect (or similar) would be very welcome.

The challenge, I’d imagine, is the fact that patches don’t necessarily have a set order. From what I understand / remember, as long as they come after their dependenc{y,ies}, it doesn’t really matter where they occur, which could possibly complicate things.

pmeunier on November 27, 2020

This would be very cool indeed.

The challenge, I’d imagine, is the fact that patches don’t necessarily have a set order.

  • A slightly inefficient version of git bisect wouldn’t be hard to write, since we have logs, and can always bisect on that.

  • A more efficient version could maybe change the implementation of tags to be able to quickly come back to tags.

  • The real challenge is to come up with something better than git bisect. I can’t really imagine how to exploit the fact that we can bisect sequences of changes rather than an entire branch. But I try to think this is due to my lack of imagination.