summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-09-09 19:54:03 (GMT)
committerJunio C Hamano <gitster@pobox.com>2014-09-09 19:54:04 (GMT)
commit067f86fe12d1d9a9a1a962f7d82b1e84adc3120a (patch)
tree6aad13e241fabcf98342f329b98c449f01d441d6 /Documentation
parent715b63ceb3c71fb748ec1e46680d96e025e9c75d (diff)
parent2d26d533a012f7475e13657d7fc829a6ba01db73 (diff)
downloadgit-067f86fe12d1d9a9a1a962f7d82b1e84adc3120a.zip
git-067f86fe12d1d9a9a1a962f7d82b1e84adc3120a.tar.gz
git-067f86fe12d1d9a9a1a962f7d82b1e84adc3120a.tar.bz2
Merge branch 'so/rebase-doc'
May need further updates to the description to explain what makes various modes of operation to decide that the request can become a "no-op". * so/rebase-doc: Documentation/git-rebase.txt: -f forces a rebase that would otherwise be a no-op
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-rebase.txt7
1 files changed, 2 insertions, 5 deletions
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 2a93c64..f14100a 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -316,11 +316,8 @@ which makes little sense.
-f::
--force-rebase::
- Force the rebase even if the current branch is a descendant
- of the commit you are rebasing onto. Normally non-interactive rebase will
- exit with the message "Current branch is up to date" in such a
- situation.
- Incompatible with the --interactive option.
+ Force a rebase even if the current branch is up-to-date and
+ the command without `--force` would return without doing anything.
+
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