3 ms·
I really really want a magit version of jujutsu. Apply the same philosophy but use jj commands to achieve it. Under the hood magit still runs git commands so th
by kccqzy 1y ago
I really really want a magit version of jujutsu. Apply the same philosophy but use jj commands to achieve it. Under the hood magit still runs git commands so there are still annoyances such as (1) the need to create branches and name them, or (2) having to resolve conflicts as they happen rather then deferring to a more convenient time in the future (first-class conflicts), or (3) the equivalent of `jj evolve` for automatic rebasing.
Also I'll have to say magit simply chose much better names than git. I never understood the `--onto` argument of `git rebase` because it's such a bad name. On the other hand magit calls it rebase subset and it's immediately clear; I now use this kind of rebase almost every day.
- syhol 1y agohave you tried lazyjj? I was thinking about giving it a go.
- kccqzy 1y agoNo because reading its GitHub it doesn't seem better than magit.
- ricericerice 1y agojjui is definitely the best contender ive seen for a jujutsu ui. although, with the ergonomics of jj, and a decent merge editor setup like meld, i haven't really needed a ui at all
- BeetleB 1y agoWhat is `jj evolve`? It's not listed as one of their commands.
- steveklabnik 1y agoElsewhere in the thread they mentioned that they meant hg evolve. This feature was originally in jj but has been gone for a while, replaced with a simpler concept. Basically, when you modify a change, jj will automatically rebase all descendants. It’s super useful!
- BeetleB 1y agoOh yeah - I know hg evolve. And yes, propagating the changes to all descendants is indeed awesome. When I first learned DVCS back around 2008-2009, I was expecting it would work that way, and was disappointed it didn't.