Looks interesting. Unfortunately doesn't support signing commits - apparently it's possible via "jj export" and using classical git:
https://github.com/martinvonz/jj/issues/58#issuecomment-1247...
Jujutsu: A Git-compatible DVCS that is both simple and powerful
41–50 of 269 posts
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#42Do I understand this correctly?
This is some kind of background process that automatically commits any changes you make.
You can use the CLI to check what it did and if you want to modify the auto commits.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#43Looks 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…
I know the nuisance of having to tiptoe around files you don't want to add to history.
In case it helps your use case:
git update-index --assume-unchanged
git update-index --no-assume-unchanged
You might find hooks useful too. Not to assume your knowledge, these are shell scripts placed in .git/hooks that are invoked, e.g., before commit or before push. You could have it parse git status, detect changes to , prompt for confirmation if changed and remove from working set if the change is unintentional.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#44This project is a great example of subliminal marketing. It is less apparent now but still, the repeated flex of “Google”, 20% project etc when no typical reader would assume them is classic corporate charlatanry. Shame because I like the project otherwise
It may be a calculated move. But, more charitably, perhaps it is simply unpolished communication.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#45Earlier quoted context omitted.
Isn't the idea that you continue editing the working copy commit until you actually commit it? Also from the documentation: https://github.com/martinvonz/jj/blob/main/docs/git-comparis... "As a Git power-user, you may think that you need the power of the index to commit only part of the working copy. However, Jujutsu provides commands for more directly achieving most use cases you're used to using Git's index for. Fo…
Sometimes you have changes that are permanent to your repo (ie local workflow), that you always want to keep locally, but never push to the remote. In git you would always leave the changes unstage, does that mean with jj you would always have to remove them before pushing? I haven’t found an answer on the linked page. Side note: I really wish git had a way to mark commit has ‘no-push’ so they never leave your local…
Isn’t this just .gitignore? I feel like I’m missing something.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#46I am certainly no expert in version control systems, but I've gotta say that it's really wonderful to see a project that builds on the algorithmic and cultural successes of Git but with a simplified and modernized approach. The reason that Git took over the open-source world is two-fold: first, it was adopted by Linux, which ended up being the most influential OSS project of all time. Second, the Git model, which is…
I am too; it's hard, now, to imagine anything dethroning git, but presumably something will do so one day, and this could be that thing.
SQLite uses a custom vcs called Fossil, but doesn't make much effort to push broader adoption (afaics) so it remains academic at this point.
Jujutsu keeping git compatibility looks like a differentiator that reduces cost of adoption. I'm excited!
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#47This looks promising. One question I had after reading about its git compatibility is that they seem mostly focused on the use case where a Jujutsu user accesses a git repository (hosted by e.g. GitHub) with jj. But does it support the converse way of working, i.e. accessing a native Jujutsu repository with git? I ask this because most developers are already quite familiar with the git CLI so in production use one wo…
The README's footnote:
At this time, there's practically no reason to use the native backend. The backend exists mainly to make sure that it's possible to eventually add functionality that cannot easily be added to the Git backend.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#48The tool looks great; I have a hurdle to overcome with the name.
I'm long accustomed to spelling it, in English, as Jujitsu. I've also seen Jiu-jitsu. "jutsu" is much less common, IME.
Is there such thing as canonical Romanisation of Nipponese? I can deal with a project being "wrong" better than not knowing which of us is wrong.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#49As I see, it is both a DVCS and a meta-DVCS.
Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful
#50This looks really cool, I'll try it out on some of my repos to get a feel for it.
Too bad support/discussion happens entirely on Discord.