News for hackers. Stuff that matters.
Re:Jujutsu Primer by zaphirplane on Friday November 20, 2026 @06:43AM (#50573360)
[delayed]
Re:Jujutsu Primer by thek3nger on Friday November 20, 2026 @06:58AM (#50573512)
The evolog doesn’t track explicit commits. It is a list of snapshots of the codebase. JJ creates a new snapshot every time you run a command (or edit a file, depending on how you configure it).
Re:Jujutsu Primer by y1n0 on Friday November 20, 2026 @09:46AM (#50575367)
[delayed]
Re:Jujutsu Primer by BeetleB on Friday November 20, 2026 @10:28AM (#50576107)
Yes, but without having to tell it to branch off.

One of the nice things about jj is you don't need to name a branch. You're just working on a graph. When you think you have something consistent and would like to give a name to it, you can do it (before or after the fact). But the lack of friction in creating a temporary new branch is amazing.

If you used VCS before git and loved how easy branching is in git, this is the same feeling in jj, but now with git being the old, tedious way.

Re:Jujutsu Primer by skydhash on Friday November 20, 2026 @10:40AM (#50576354)
> One of the nice things about jj is you don't need to name a branch.

Maybe it's due to different thinking process. But I can't think of doing a branch without knowing why I would need to do it, which also give me a quick indication of how I should name it. Everything is local anyway so I don't complicate stuff.

Re:Jujutsu Primer by steveklabnik on Friday November 20, 2026 @12:24PM (#50578409)
You see the description of changes in your log, and so that's often good enough as a name. No need to give it a second one. Here's an example from a project of mine:

    │ ○  lrvwrmqv [email protected] 2026-09-07 22:13:12 977b1ab7
    │ │  harden running image identity fixtures
    │ ○  vqmsmkup [email protected] 2026-09-07 22:13:12 bcd98591
    ├─╯  add running compiler image identity
    ◆  mxvotmyz [email protected] 2026-09-07 21:53:55 trunk e37a132e
    │  satisfy the byte recovery Clippy gate
It's nicer with color. Anyway, this is an anonymous branch, with two changes on it. "add running compiler image identity" and "harden running image identity fixtures" let me know what that branch is about, without needing to add an extra name onto the branch itself.
Re:Jujutsu Primer by skydhash on Friday November 20, 2026 @02:03PM (#50580055)
I've just replied to another comment of yours

https://news.ycombinator.com/item?id=50577902

But the relevant bit to this is the following

  I want tooling centered around the concept of a patch, not the concept of commits.
Commits for me are settled patches. I don't go around editing commits that much (and I have the tooling to make it trivial). Because for me, the patch inside has served it purpose. When I found a new purpose for it, the context has already been changed, so even when it saved me a bit of typing, I had to look at it anew.

So only the few commits around my current tasks are in flux. There's not a lot, so rebasing is very easy, even with the git cli. Same with editing a span of commits. It becomes the workspace and thus can easily be modified. Everything else is just on hold. That's why I like named branch. Because I look at it holistically instead of individual commits.

Maybe your workflow is different, and you are always doing surgical treatment to a complicated tree. But I never needed to do so. These days I'm even leaning towards a single patch for a feature or a fix. Way easier for communication.

EDIT

reply slowed down by HN moderation.

Re:Jujutsu Primer by dwattttt on Friday November 20, 2026 @02:20PM (#50580354)
Other people mentioned it, but since it was what I did; I didn't commit the day before/that morning. I didn't realise I'd need that morning's version, I only realised that after mutating it.

So it's the "oh no, I realise now that I needed to commit before I made all those changes" situation, but since the workspace gets snapshot/committed on every jj command, nothing was lost.