Jujutsu: A Git-compatible DVCS that is both simple and powerful
1–10 of 269 posts
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#2Oh wow, this looks really promising.
I've been playing with a homegrown centralized VCS client and server project, aimed at basically being the VCS host for monorepos, and this looks like a much better foundation for the VCS layer.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#3Jujutsu started as author's personal project and now author's full-time project at Google. It's presented at Git Merge 2022:
Jujutsu: A Git-Compatible VCS - Git Merge 2022:
Video:
Slides:
https://docs.google.com/presentation/d/1F8j9_UOOSGUN9MvHxPZX...
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#4I had to choose a VCS for a project a year ago. At that point jujutsu looked extremely promising but immature. It's great to see that so much progress has been made. I can't wait to give it another go, the next time I get to choose a VCS for something. Innovation in this space is desperately needed.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#5I would say "What a weird name for a VCS. Whether that will work ...", but then I have to remind myself of the dictionary meaning of "git". So who knows. Maybe we will be adopting all kinds of martial arts terminology. For example: "I use Karate to manage my code. I divide everything using chops. When a kata is done, ..."
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#6I'm definitely going to try this, looks really sweet.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#7The automatic rebase and jj diffedit sound very nice addition to some of my most-used git workflows.
Looks very interesting, will definitely have to give this a deeper try.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#8Looks really cool! One thing I'm not clear on from the docs: does it support ignoring changes to some files for "real" commits? For example, a repo at work has a file used for mocking up feature flags. The file is tracked but it's encouraged to edit it when testing things, just don't commit your changes. If I'm not mistaken, I'd have to remember to undo changes to that file before "describing" the commit. Is that right?
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#9Explain how does it handle large binary files?
(the UX around this is the shortcoming of all current DVCS..)
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#10Looks really cool! One thing I'm not clear on from the docs: does it support ignoring changes to some files for "real" commits? For example, a repo at work has a file used for mocking up feature flags. The file is tracked but it's encouraged to edit it when testing things, just don't commit your changes. If I'm not mistaken, I'd have to remember to undo changes to that file before "describing" the commit. Is that rig…
The commit will indeed be created immediately, there's no way to prevent that except for .gitignore I'm aware of. Until you run `jj describe`, it won't have a description.
However, if you don't manually put a branch on it, it'll never get pushed and will stay on your machine only.
You can sit on this personal commit and rebase it on top of any other commit to move around the repo, again and again if you like.