git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Documentation/git-rebase: clarify -s option

From
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Date
Nov 12, 2010, 18:57 UTC
Message-ID
<1289588269-6920-1-git-send-email-martin.von.zweigbergk@gmail.com>

Clarify that it is '-s' itself that implies '--merge'. Currently it may seem like '--merge' is implied "If there is no `-s` option".

Signed-off-by: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
---
 Documentation/git-rebase.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 30e5c0e..f3753a8 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -244,9 +244,9 @@ other words, the sides are swapped.
 
 -s <strategy>::
 --strategy=<strategy>::
-	Use the given merge strategy.
+	Use the given merge strategy.  This implies --merge.
 	If there is no `-s` option 'git merge-recursive' is used
-	instead.  This implies --merge.
+	instead.
 +
 Because 'git rebase' replays each commit from the working branch
 on top of the <upstream> branch using the given strategy, using
-- 
1.7.3.2.167.ga361b
Next: Junio C Hamano
Message 1 of 2 in “Documentation/git-rebase: clarify -s option”
  1. Documentation/git-rebase: clarify -s optionMartin von Zweigbergk, Nov 12, 2010
  2. Junio C HamanoNov 13, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.