←back to thread

Jujutsu worktrees are convenient (2024)

(shaddy.dev)
128 points nvader | 1 comments | 03 Dec 25 23:26 UTC | HN request time: 0.278s | source
Show context
rafaelmn ◴[08 Dec 25 10:15 UTC] No.46190591[source]▶
So how is this different from git worktrees exactly ?
replies(2): >>46190753 #>>46191208 #
rk06 ◴[08 Dec 25 10:38 UTC] No.46190753[source]▶
there is no difference as jj is only a frontend to git.

author me tions that git cli require multiple steps when there are unstaged changes.

I don't know if git has one liner cli command for it as i myself use gitextn to create worktrees

replies(3): >>46190898 #>>46191762 #>>46201886 #
dubi_steinkek ◴[08 Dec 25 10:59 UTC] No.46190898[source]▶
> there is no difference as jj is only a frontend to git.

That's not really true in this case, as the worktree feature from jujutsu is not implemented on top of git worktrees.

replies(2): >>46191425 #>>46192334 #
rk06 ◴[08 Dec 25 14:05 UTC] No.46192334[source]▶
wtf? it can diverge from git?

wasn't git compatibility it's main pro?

replies(5): >>46193172 #>>46194310 #>>46194774 #>>46198872 #>>46201894 #
1. steveklabnik ◴[08 Dec 25 16:32 UTC] No.46194310[source]▶
Yes, jj is its own VCS with pluggable backends.

Google uses it with Piper, their centralized VCS.

Being compatible and being purely a frontend aren’t the same thing.