←back to thread

128 points nvader | 1 comments | | HN request time: 0.224s | source
Show context
rafaelmn ◴[] No.46190591[source]
So how is this different from git worktrees exactly ?
replies(2): >>46190753 #>>46191208 #
rk06 ◴[] 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 ◴[] 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 #
Macha ◴[] No.46191425[source]
This is kind of unfortunate in this case as it breaks some tooling since the extra trees are not collocated with git, like editor inline history/blame or agents that know to look in git history to fix their mistakes
replies(2): >>46191784 #>>46194292 #
1. steveklabnik ◴[] No.46194292[source]
The fix for having worktrees be colocated is in progress. Not sure when it’ll be done but it’s coming.