←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.001s | 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 #
weinzierl ◴[08 Dec 25 11:49 UTC] No.46191208[source]▶
In git you can have only one worktree per branch. For example, if you have a worktree on main you cannot have another one on main.

I personally find this annoying. I usually like to keep one pristine and always current working copy of main (and develop if applicable) around for search and other analysis tasks[1]. Worktrees would be ideal and efficient but due to the mentioned restriction I have to either waste space for a separate clone or do some ugly workarounds to keep the worktree on the branch while not keeping it on the branch.

jujutsu workspace are much nicer in that regard.

[1] I know there are tons of ways search and analyze in git but over the years I found a pristine working copy to be the most versatile solution.

replies(6): >>46191261 #>>46191697 #>>46191865 #>>46192204 #>>46194289 #>>46197961 #
1. 1718627440 ◴[08 Dec 25 21:35 UTC] No.46197961[source]▶
> In git you can have only one worktree per branch.

Well, that is true, but a branch is nothing more than an automoving label, so I don't see how that is limiting at all. You can have as many branches as you like and you can also just checkout the commit.