summaryrefslogtreecommitdiff
path: root/t/t6135-pathspec-with-attrs.sh
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2018-03-06 14:54:04 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-03-06 14:54:04 -0800
commitf88590e67580572acd9c2f61fe4d652b9b2c779d (patch)
tree46d5f07dfc524dc0c1aa1cb012011d8fa441c24a /t/t6135-pathspec-with-attrs.sh
parentMerge branch 'ab/simplify-perl-makefile' (diff)
parentmerge: allow fast-forward when merging a tracked tag (diff)
downloadtgif-f88590e67580572acd9c2f61fe4d652b9b2c779d.tar.xz
Merge branch 'jc/allow-ff-merging-kept-tags'
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
Diffstat (limited to 't/t6135-pathspec-with-attrs.sh')
0 files changed, 0 insertions, 0 deletions