Skip to content

Commit 981ce57

Browse files
jvnsgitster
authored andcommitted
doc: git-rebase: move --onto explanation down
There's a very clear explanation with examples of using --onto which is currently buried in the very long DESCRIPTION section. This moves it to its own section, so that we can reference the explanation from the `--onto` option by name. Signed-off-by: Julia Evans <julia@jvns.ca> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 1469715 commit 981ce57

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

Documentation/git-rebase.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,9 @@ will result in:
114114
D---E---A'---F master
115115
------------
116116

117+
TRANSPLANTING A TOPIC BRANCH WITH --ONTO
118+
----------------------------------------
119+
117120
Here is how you would transplant a topic branch based on one
118121
branch to another, to pretend that you forked the topic branch
119122
from the latter branch, using `rebase --onto`.
@@ -240,6 +243,8 @@ As a special case, you may use "A\...B" as a shortcut for the
240243
merge base of A and B if there is exactly one merge base. You can
241244
leave out at most one of A and B, in which case it defaults to HEAD.
242245

246+
See TRANSPLANTING A TOPIC BRANCH WITH --ONTO above for examples.
247+
243248
--keep-base::
244249
Set the starting point at which to create the new commits to the
245250
merge base of `<upstream>` and `<branch>`. Running

0 commit comments

Comments
 (0)