Commit a414684e authored by Uwe Kleine-König's avatar Uwe Kleine-König Committed by Jonathan Corbet

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: default avatarUwe Kleine-König <uwe@kleine-koenig.org>
[jc: rewrote changelog]
Link: https://lore.kernel.org/r/20230228134657.1797871-1-u.kleine-koenig@pengutronix.deSigned-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 0b02076f
...@@ -213,11 +213,7 @@ point rather than some random spot. If your upstream-bound branch has ...@@ -213,11 +213,7 @@ point rather than some random spot. If your upstream-bound branch has
emptied entirely into the mainline during the merge window, you can pull it emptied entirely into the mainline during the merge window, you can pull it
forward with a command like:: forward with a command like::
git merge v5.2-rc1^0 git merge --ff-only v5.2-rc1
The "^0" will cause Git to do a fast-forward merge (which should be
possible in this situation), thus avoiding the addition of a spurious merge
commit.
The guidelines laid out above are just that: guidelines. There will always The guidelines laid out above are just that: guidelines. There will always
be situations that call out for a different solution, and these guidelines be situations that call out for a different solution, and these guidelines
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment