Skip to content

Commit a414684

Browse files
ukleinekJonathan Corbet
authored andcommitted
docs: rebasing-and-merging: Drop wrong statement about git
The "^0" syntax is no longer needed to fast-forward to a mainline commit; take that out and add --ff-only to force an error if fast-forward is not possible. Signed-off-by: Uwe Kleine-König <[email protected]> [jc: rewrote changelog] Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jonathan Corbet <[email protected]>
1 parent 0b02076 commit a414684

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

Documentation/maintainer/rebasing-and-merging.rst

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -213,11 +213,7 @@ point rather than some random spot. If your upstream-bound branch has
213213
emptied entirely into the mainline during the merge window, you can pull it
214214
forward with a command like::
215215

216-
git merge v5.2-rc1^0
217-
218-
The "^0" will cause Git to do a fast-forward merge (which should be
219-
possible in this situation), thus avoiding the addition of a spurious merge
220-
commit.
216+
git merge --ff-only v5.2-rc1
221217

222218
The guidelines laid out above are just that: guidelines. There will always
223219
be situations that call out for a different solution, and these guidelines

0 commit comments

Comments
 (0)