summaryrefslogtreecommitdiff
path: root/weblog/jujutsu-is-the-real-deal.md
diff options
context:
space:
mode:
Diffstat (limited to 'weblog/jujutsu-is-the-real-deal.md')
-rw-r--r--weblog/jujutsu-is-the-real-deal.md4
1 files changed, 2 insertions, 2 deletions
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`