Jujutsu (jj), a Git compatible VCS
tonyfinn.com
Jujutsu (jj), a Git compatible VCS
1–10 of 117 posts
Re: Jujutsu (jj), a Git compatible VCS
#2I'm still unsure of why I'd want to move to jj from git.
My ideal git workflow is pretty simple:
1. `git switch -C new-branch` 2. Make changes, time passes 3. `git add .` 4. `git commit -m "Description of changes made"` 5. `git fetch && git rebase origin/main` 6. `git push` 7. Make pr to main
If main is out of date I rebase again to update.
This to me feels pretty light weight and is not a hinderence in any way on my day to day tasks.
What exactly makes `jj` better? Is there a specific usecase i'm not understanding?
Re: Jujutsu (jj), a Git compatible VCS
#3I'm still unsure of why I'd want to move to jj from git. My ideal git workflow is pretty simple: 1. `git switch -C new-branch` 2. Make changes, time passes 3. `git add .` 4. `git commit -m "Description of changes made"` 5. `git fetch && git rebase origin/main` 6. `git push` 7. Make pr to main If main is out of date I rebase again to update. This to me feels pretty light weight and is not a hinderence in any way on my…
One advantage is that jujutsu tracks merge conflicts so you don't end up in a situation where you'll have to resolve the same conflict more than once, which may sometimes happen with git.
Re: Jujutsu (jj), a Git compatible VCS
#4I'm still unsure of why I'd want to move to jj from git. My ideal git workflow is pretty simple: 1. `git switch -C new-branch` 2. Make changes, time passes 3. `git add .` 4. `git commit -m "Description of changes made"` 5. `git fetch && git rebase origin/main` 6. `git push` 7. Make pr to main If main is out of date I rebase again to update. This to me feels pretty light weight and is not a hinderence in any way on my…
One advantage is that jujutsu tracks merge conflicts so you don't end up in a situation where you'll have to resolve the same conflict more than once, which may sometimes happen with git.
But why build a whole VCS around that one use case? I looked through the docs and honestly it looks like it complicates life instead of making it easier.
edit: everyone is so focused on the "single use case" part and not the fact that it looks more complicated and verbose than regular git. Unless everyone using it is some git god that runs into edge cases left and right... maybe my workflow is just not that complicated to need a solution to problems I don't have?
Re: Jujutsu (jj), a Git compatible VCS
#5If Jujutsu ever picks up steam and becomes a replacement of Git, I wish the Github version for it will be called Kaisen.
Re: Jujutsu (jj), a Git compatible VCS
#6If Jujutsu ever picks up steam and becomes a replacement of Git, I wish the Github version for it will be called Kaisen.
why?
Re: Jujutsu (jj), a Git compatible VCS
#7Re: Jujutsu (jj), a Git compatible VCS
#8I'm still unsure of why I'd want to move to jj from git. My ideal git workflow is pretty simple: 1. `git switch -C new-branch` 2. Make changes, time passes 3. `git add .` 4. `git commit -m "Description of changes made"` 5. `git fetch && git rebase origin/main` 6. `git push` 7. Make pr to main If main is out of date I rebase again to update. This to me feels pretty light weight and is not a hinderence in any way on my…
One advantage is that jujutsu tracks merge conflicts so you don't end up in a situation where you'll have to resolve the same conflict more than once, which may sometimes happen with git.
Git’s rerere functionality should address this, right?
Re: Jujutsu (jj), a Git compatible VCS
#9If Jujutsu ever picks up steam and becomes a replacement of Git, I wish the Github version for it will be called Kaisen.
why?
Re: Jujutsu (jj), a Git compatible VCS
#10I'm still unsure of why I'd want to move to jj from git. My ideal git workflow is pretty simple: 1. `git switch -C new-branch` 2. Make changes, time passes 3. `git add .` 4. `git commit -m "Description of changes made"` 5. `git fetch && git rebase origin/main` 6. `git push` 7. Make pr to main If main is out of date I rebase again to update. This to me feels pretty light weight and is not a hinderence in any way on my…
One advantage is that jujutsu tracks merge conflicts so you don't end up in a situation where you'll have to resolve the same conflict more than once, which may sometimes happen with git.
So it is git with rerere.enabled=1?