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

[PATCH] rebase docs: drop stray word in merge command description

From
Kyle Meyer <kyle@kyleam.com>
Date
Dec 8, 2018, 23:15 UTC
Message-ID
<20181208231541.1341999-1-kyle@kyleam.com>

Delete a misplaced word introduced by caafecfcf1 (rebase --rebase-merges: adjust man page for octopus support, 2018-03-09).

Signed-off-by: Kyle Meyer <kyle@kyleam.com>
---
 Documentation/git-rebase.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index dff17b3178..2ee535fb23 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -979,7 +979,7 @@ when the merge operation did not even start), it is rescheduled immediately.
 
 At this time, the `merge` command will *always* use the `recursive`
 merge strategy for regular merges, and `octopus` for octopus merges,
-strategy, with no way to choose a different one. To work around
+with no way to choose a different one. To work around
 this, an `exec` command can be used to call `git merge` explicitly,
 using the fact that the labels are worktree-local refs (the ref
 `refs/rewritten/onto` would correspond to the label `onto`, for example).
-- 
2.19.2
Next: Johannes Schindelin
Message 1 of 4 in “rebase docs: drop stray word in merge command description”
  1. rebase docs: drop stray word in merge command descriptionKyle Meyer, Dec 8, 2018
  2. Johannes SchindelinDec 9, 2018
  3. Junio C HamanoDec 10, 2018
  4. Johannes SchindelinDec 10, 2018

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.