Merge branch 'jc/allow-ff-merging-kept-tags' into jch
authorJunio C Hamano <gitster@pobox.com>
Fri, 23 Feb 2018 21:27:53 +0000 (13:27 -0800)
committerJunio C Hamano <gitster@pobox.com>
Fri, 23 Feb 2018 21:27:53 +0000 (13:27 -0800)
commita01704032bf89ee4a0fa736084b52e99b6cdcddb
treef0aa80ba7f8e763a0ca04ad1bd66110d4ba7d4ce
parent612d5b051b5ce1bbc31b74a7290aa671b1bf3e08
parentadcc94a0aa7055be4133ebda8b25f4af63285c6d
Merge branch 'jc/allow-ff-merging-kept-tags' into jch

Since Git 1.7.9, "git merge" defaulted to --no-ff (i.e. even when
the side branch being merged is a descendant of the current commit,
create a merge commit instead of fast-forwarding) when merging a
tag object.  This was appropriate default for integrators who pull
signed tags from their downstream contributors, but caused an
unnecessary merges when used by downstream contributors who
habitually "catch up" their topic branches with tagged releases
from the upstream.  Update "git merge" to default to --no-ff only
when merging a tag object that does *not* sit at its usual place in
refs/tags/ hierarchy, and allow fast-forwarding otherwise, to
mitigate the problem.

* jc/allow-ff-merging-kept-tags:
  merge: allow fast-forward when merging a tracked tag
builtin/merge.c