5 ms·
> As a trivial counter example Git does not currently have a way to store conflicts inside commits[1], which is one of our major features. Yes, I like how jj d
by KajMagnus 16d ago
> As a trivial counter example Git does not currently have a way to store conflicts inside commits[1], which is one of our major features.
Yes, I like how jj does it!
Did a big `git rebase -i` yesterday and I felt stressed up, almost a bit angry, when there were some conflicts and I wasn't sure if I'd resolve all of them before it was time to leave, and work more later from a different laptop.
But with jj, no stress: I can just check in the conflicts, and later, on the other laptop: check out the conflicts and continue resolving.
(I just wish there was Git submodule support :- ))
- stouset 15d agoAnd you can deal with them in any order, bit by bit, or by adjusting things in earlier commits. I no longer fear rebase conflicts.
- deleted 15d ago[deleted]
- 1718627440 15d agoI mean that's what I do in Git as well, I just don't do it by storing conflicts, but by not triggering them/ignoring them.