mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'so/rebase-doc' into maint

Browse Source 
* so/rebase-doc:
  Documentation/git-rebase.txt: <upstream> must be given to specify <branch>
  Documentation/git-rebase.txt: -f forces a rebase that would otherwise be a no-op
This commit is contained in:
Junio C Hamano
2014-09-29 22:08:12 -07:00
parent 62b553cdd6 95c68267ff
commit e7867e80f0
1 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Documentation/git-rebase.txt
View File

@ -9,7 +9,7 @@ SYNOPSIS
-------- --------
[verse] [verse]
'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>] 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>]
[<upstream>] [<branch>] [<upstream> [<branch>]]
'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>] 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>]
--root [<branch>] --root [<branch>]
'git rebase' --continue | --skip | --abort | --edit-todo 'git rebase' --continue | --skip | --abort | --edit-todo
@ -316,11 +316,8 @@ which makes little sense.
-f:: -f::
--force-rebase:: --force-rebase::
Force the rebase even if the current branch is a descendant Force a rebase even if the current branch is up-to-date and
of the commit you are rebasing onto. Normally non-interactive rebase will the command without `--force` would return without doing anything.
exit with the message "Current branch is up to date" in such a
situation.
Incompatible with the --interactive option.
+ +
You may find this (or --no-ff with an interactive rebase) helpful after You may find this (or --no-ff with an interactive rebase) helpful after
reverting a topic branch merge, as this option recreates the topic branch with reverting a topic branch merge, as this option recreates the topic branch with