| commit | f51a48ec3aacaa01357c891c79dfc45aae0efeff | |
| author | Sergey Organov <sorganov@gmail.com> | |
| Thu, 18 Sep 2014 19:03:25 +0000 (18 23:03 +0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 29 Sep 2014 16:30:04 +0000 (29 09:30 -0700) | ||
| tree | 3d47986230e1bc188149c96e2a9082c6be1446d2 | treesnapshot (tar.gz zip) |
| parent | d31f3ad23dd1aee3c3e1015a43b02b995c01a9a1 | commitdiff |
Documentation/git-rebase.txt: document when --fork-point is auto-enabled
Running "git rebase" without giving a specific commit with respect
to which the operation is done enables --fork-point mode, while
telling the command to rebase with respect to a specific commit,
i.e. "git rebase <upstream>" does not.
This was not mentioned in the DESCRIPTION section of the manual
page, even though the case of omitted <upstream> was otherwise
discussed. That in turn made actual behavior of vanilla "git
rebase" hardly discoverable.
While we are at it, clarify the --fork-point description itself as
well.
Signed-off-by: Sergey Organov <sorganov@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Running "git rebase" without giving a specific commit with respect
to which the operation is done enables --fork-point mode, while
telling the command to rebase with respect to a specific commit,
i.e. "git rebase <upstream>" does not.
This was not mentioned in the DESCRIPTION section of the manual
page, even though the case of omitted <upstream> was otherwise
discussed. That in turn made actual behavior of vanilla "git
rebase" hardly discoverable.
While we are at it, clarify the --fork-point description itself as
well.
Signed-off-by: Sergey Organov <sorganov@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-rebase.txt | diffblobblamehistory |