| OLD | NEW |
| (Empty) |
| 1 git-reparent-branch(1) | |
| 2 ===================== | |
| 3 | |
| 4 NAME | |
| 5 ---- | |
| 6 git-reparent-branch - | |
| 7 include::_git-reparent-branch_desc.helper.txt[] | |
| 8 | |
| 9 SYNOPSIS | |
| 10 -------- | |
| 11 [verse] | |
| 12 'git reparent-branch' <new_parent> | |
| 13 'git reparent-branch' --lkgr | |
| 14 'git reparent-branch' --root | |
| 15 | |
| 16 DESCRIPTION | |
| 17 ----------- | |
| 18 | |
| 19 Change the 'upstream' of the current branch, and then run | |
| 20 linkgit:git-rebase-update[1] to move the commits in the current branch, as well | |
| 21 as the commits in all descendant branches, onto the new parent. | |
| 22 | |
| 23 `<new_parent>` may be either a local branch, remote branch, OR a tag (such as | |
| 24 `lkgr`). | |
| 25 | |
| 26 This is particularly useful to reparent an independent CL to become dependent on | |
| 27 another CL, or vice versa. This could happen if you started both on the | |
| 28 assumption that they were independent, but later realized that this was not the | |
| 29 case. | |
| 30 | |
| 31 | |
| 32 OPTIONS | |
| 33 ------- | |
| 34 | |
| 35 <new_parent>:: | |
| 36 The new parent to set as the upstream for this branch. May be a branch ref or | |
| 37 a tag. | |
| 38 | |
| 39 --lkgr:: | |
| 40 Reparent to track lkgr. | |
| 41 | |
| 42 --root:: | |
| 43 Reparent to track the 'root' branch. Defaults to 'origin/master'. See | |
| 44 linkgit:git-new-branch[1]'s CONFIGURATION VARIABLES section.. | |
| 45 | |
| 46 | |
| 47 include::_aliases.txt[] | |
| 48 | |
| 49 ---- | |
| 50 [alias] | |
| 51 git rp = reparent-branch | |
| 52 ---- | |
| 53 | |
| 54 SEE ALSO | |
| 55 -------- | |
| 56 linkgit:git-rebase-update[1], linkgit:git-rename-branch[1], | |
| 57 linkgit:git-new-branch[1], linkgit:git-upstream-diff[1] | |
| 58 | |
| 59 include::_footer.txt[] | |
| 60 | |
| 61 // vim: ft=asciidoc: | |
| OLD | NEW |