From 0e602cfa7881f789c3e9f1d5f25db9a8179cd0fc Mon Sep 17 00:00:00 2001 From: t Date: Sun, 12 Jul 2026 20:00:15 -0600 Subject: site updates --- weblog/jujutsu-is-the-real-deal.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'weblog/jujutsu-is-the-real-deal.md') diff --git a/weblog/jujutsu-is-the-real-deal.md b/weblog/jujutsu-is-the-real-deal.md index 83ba324..3f1216e 100644 --- a/weblog/jujutsu-is-the-real-deal.md +++ b/weblog/jujutsu-is-the-real-deal.md @@ -2,6 +2,8 @@ post_date: 2025-03-22 --- +> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp` + # Jujutsu is the Real Deal An experience report from using jj as my primary git frontend for a few months. @@ -45,5 +47,3 @@ All this is great, but plenty of later VCSes can claim to be better than git in So when I said "You can view JJ as a really simple automation of this \[git\] workflow", I *really* meant that. This is also why the revision objects within jj's changes are so much like git's commits - they actually are git commits. I've been using jj now for about 6 weeks as my *only* VCS tool, and have continued uninterrupted working with a team that uses git and github. There's really no reason not to give it a go. ~tjp - -> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp` -- cgit v1.3