From 0907c48653341d39e306c2935859944aeb6479c2 Mon Sep 17 00:00:00 2001
From: Marcello Lamonaca <marcello@lamonaca.eu>
Date: Mon, 6 May 2024 10:26:12 +0200
Subject: [PATCH] git: refine reabse 'onto' notes

---
 docs/misc/git.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/misc/git.md b/docs/misc/git.md
index a86584f..1edc687 100644
--- a/docs/misc/git.md
+++ b/docs/misc/git.md
@@ -190,7 +190,7 @@ It's generally recommended creating annotated tags so it's possible to have all
 `git merge <branch-name>`: merges into current branch  
 `git merge --continue`: continue previous merge after solving a merge conflict  
 `git rebase <branch>`: rebase current branch commits onto another branch  
-`git rebase --onto <commit>`: rebase current branch commits onto another commit  
+`git rebase --onto <new-base> <old-base>`: rebase a slice of commits from `<old-base>` onto `<new-base>`  
 
 `git cherry-pick <commit>`: bring in a commit from another branch  
 `git cherry-pick <commit>..<commit>`: bring in a range of commits from another branch (first excluded)