diff options
author | Junio C Hamano <gitster@pobox.com> | 2013-03-21 22:57:48 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-03-21 15:47:38 -0700 |
commit | 77c72780edfa5e3858423366fc91699724793b39 (patch) | |
tree | a99b3e5cd412ea5ddd2c4119d5c88d49d3dbabec /Documentation/merge-options.txt | |
parent | 5d417842efeafb6e109db7574196901c4e95d273 (diff) | |
download | git-77c72780edfa5e3858423366fc91699724793b39.tar.gz |
Documentation: merging a tag is a special case
When asking Git to merge a tag (such as a signed tag or annotated tag),
it will always create a merge commit even if fast-forward was possible.
It's like having --no-ff present on the command line.
It's a difference from the default behavior described in git-merge.txt.
It should be documented as an exception of "FAST-FORWARD MERGE" section
and "--ff" option description.
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Reviewed-by: Yann Droneaud <ydroneaud@opteya.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/merge-options.txt')
-rw-r--r-- | Documentation/merge-options.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/merge-options.txt b/Documentation/merge-options.txt index 0bcbe0ac3c..34a8445828 100644 --- a/Documentation/merge-options.txt +++ b/Documentation/merge-options.txt @@ -30,7 +30,8 @@ set to `no` at the beginning of them. --no-ff:: Create a merge commit even when the merge resolves as a - fast-forward. + fast-forward. This is the default behaviour when merging an + annotated (and possibly signed) tag. --ff-only:: Refuse to merge and exit with a non-zero status unless the |