2005-11-11 12:00:52 +03:00
|
|
|
#!/bin/sh
|
|
|
|
#
|
|
|
|
# Copyright (c) 2005 Junio C Hamano
|
|
|
|
#
|
|
|
|
|
2010-08-17 11:01:54 +04:00
|
|
|
test_description='Merge base and parent list computation.
|
2005-11-11 12:00:52 +03:00
|
|
|
'
|
|
|
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
M=1130000000
|
|
|
|
Z=+0000
|
2010-08-17 10:57:12 +04:00
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
GIT_COMMITTER_EMAIL=git@comm.iter.xz
|
|
|
|
GIT_COMMITTER_NAME='C O Mmiter'
|
|
|
|
GIT_AUTHOR_NAME='A U Thor'
|
|
|
|
GIT_AUTHOR_EMAIL=git@au.thor.xz
|
|
|
|
export GIT_COMMITTER_EMAIL GIT_COMMITTER_NAME GIT_AUTHOR_NAME GIT_AUTHOR_EMAIL
|
2010-08-17 10:57:12 +04:00
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
doit () {
|
|
|
|
OFFSET=$1 &&
|
|
|
|
NAME=$2 &&
|
|
|
|
shift 2 &&
|
2010-08-17 10:57:12 +04:00
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
PARENTS= &&
|
|
|
|
for P
|
|
|
|
do
|
|
|
|
PARENTS="${PARENTS}-p $P "
|
|
|
|
done &&
|
2010-08-17 10:57:12 +04:00
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
GIT_COMMITTER_DATE="$(($M + $OFFSET)) $Z" &&
|
|
|
|
GIT_AUTHOR_DATE=$GIT_COMMITTER_DATE &&
|
|
|
|
export GIT_COMMITTER_DATE GIT_AUTHOR_DATE &&
|
2010-08-17 10:57:12 +04:00
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
commit=$(echo $NAME | git commit-tree $T $PARENTS) &&
|
2010-08-17 10:57:12 +04:00
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
echo $commit >.git/refs/tags/$NAME &&
|
|
|
|
echo $commit
|
|
|
|
}
|
2010-08-17 10:57:12 +04:00
|
|
|
|
2011-05-07 00:58:52 +04:00
|
|
|
test_expect_success 'setup' '
|
|
|
|
T=$(git mktree </dev/null)
|
2010-08-17 10:57:12 +04:00
|
|
|
'
|
2006-07-05 04:35:20 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
test_expect_success 'set up G and H' '
|
|
|
|
# E---D---C---B---A
|
|
|
|
# \"-_ \ \
|
|
|
|
# \ `---------G \
|
|
|
|
# \ \
|
|
|
|
# F----------------H
|
|
|
|
E=$(doit 5 E) &&
|
|
|
|
D=$(doit 4 D $E) &&
|
|
|
|
F=$(doit 6 F $E) &&
|
|
|
|
C=$(doit 3 C $D) &&
|
|
|
|
B=$(doit 2 B $C) &&
|
|
|
|
A=$(doit 1 A $B) &&
|
|
|
|
G=$(doit 7 G $B $E) &&
|
|
|
|
H=$(doit 8 H $A $F)
|
|
|
|
'
|
2006-07-05 04:35:20 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
test_expect_success 'merge-base G H' '
|
|
|
|
git name-rev $B >expected &&
|
2006-07-05 04:35:20 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
MB=$(git merge-base G H) &&
|
|
|
|
git name-rev "$MB" >actual.single &&
|
2006-07-05 04:35:20 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
MB=$(git merge-base --all G H) &&
|
|
|
|
git name-rev "$MB" >actual.all &&
|
2006-07-05 04:35:20 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
MB=$(git show-branch --merge-base G H) &&
|
|
|
|
git name-rev "$MB" >actual.sb &&
|
2006-07-05 04:35:20 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
test_cmp expected actual.single &&
|
|
|
|
test_cmp expected actual.all &&
|
|
|
|
test_cmp expected actual.sb
|
|
|
|
'
|
2009-08-05 11:59:18 +04:00
|
|
|
|
2010-08-17 11:01:54 +04:00
|
|
|
test_expect_success 'merge-base/show-branch --independent' '
|
|
|
|
git name-rev "$H" >expected1 &&
|
|
|
|
git name-rev "$H" "$G" >expected2 &&
|
|
|
|
|
|
|
|
parents=$(git merge-base --independent H) &&
|
|
|
|
git name-rev $parents >actual1.mb &&
|
|
|
|
parents=$(git merge-base --independent A H G) &&
|
|
|
|
git name-rev $parents >actual2.mb &&
|
|
|
|
|
|
|
|
parents=$(git show-branch --independent H) &&
|
|
|
|
git name-rev $parents >actual1.sb &&
|
|
|
|
parents=$(git show-branch --independent A H G) &&
|
|
|
|
git name-rev $parents >actual2.sb &&
|
|
|
|
|
|
|
|
test_cmp expected1 actual1.mb &&
|
|
|
|
test_cmp expected2 actual2.mb &&
|
|
|
|
test_cmp expected1 actual1.sb &&
|
|
|
|
test_cmp expected2 actual2.sb
|
|
|
|
'
|
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
test_expect_success 'unsynchronized clocks' '
|
|
|
|
# This test is to demonstrate that relying on timestamps in a distributed
|
|
|
|
# SCM to provide a _consistent_ partial ordering of commits leads to
|
|
|
|
# insanity.
|
|
|
|
#
|
|
|
|
# Relative
|
|
|
|
# Structure timestamps
|
|
|
|
#
|
|
|
|
# PL PR +4 +4
|
|
|
|
# / \/ \ / \/ \
|
|
|
|
# L2 C2 R2 +3 -1 +3
|
|
|
|
# | | | | | |
|
|
|
|
# L1 C1 R1 +2 -2 +2
|
|
|
|
# | | | | | |
|
|
|
|
# L0 C0 R0 +1 -3 +1
|
|
|
|
# \ | / \ | /
|
|
|
|
# S 0
|
|
|
|
#
|
|
|
|
# The left and right chains of commits can be of any length and complexity as
|
|
|
|
# long as all of the timestamps are greater than that of S.
|
|
|
|
|
|
|
|
S=$(doit 0 S) &&
|
|
|
|
|
|
|
|
C0=$(doit -3 C0 $S) &&
|
|
|
|
C1=$(doit -2 C1 $C0) &&
|
|
|
|
C2=$(doit -1 C2 $C1) &&
|
|
|
|
|
|
|
|
L0=$(doit 1 L0 $S) &&
|
|
|
|
L1=$(doit 2 L1 $L0) &&
|
|
|
|
L2=$(doit 3 L2 $L1) &&
|
|
|
|
|
|
|
|
R0=$(doit 1 R0 $S) &&
|
|
|
|
R1=$(doit 2 R1 $R0) &&
|
|
|
|
R2=$(doit 3 R2 $R1) &&
|
|
|
|
|
|
|
|
PL=$(doit 4 PL $L2 $C2) &&
|
2010-10-31 04:46:54 +03:00
|
|
|
PR=$(doit 4 PR $C2 $R2) &&
|
2010-08-17 10:57:12 +04:00
|
|
|
|
|
|
|
git name-rev $C2 >expected &&
|
|
|
|
|
|
|
|
MB=$(git merge-base PL PR) &&
|
|
|
|
git name-rev "$MB" >actual.single &&
|
|
|
|
|
|
|
|
MB=$(git merge-base --all PL PR) &&
|
|
|
|
git name-rev "$MB" >actual.all &&
|
|
|
|
|
|
|
|
test_cmp expected actual.single &&
|
|
|
|
test_cmp expected actual.all
|
|
|
|
'
|
2008-07-30 10:51:41 +04:00
|
|
|
|
2010-08-17 11:01:54 +04:00
|
|
|
test_expect_success '--independent with unsynchronized clocks' '
|
|
|
|
IB=$(doit 0 IB) &&
|
|
|
|
I1=$(doit -10 I1 $IB) &&
|
|
|
|
I2=$(doit -9 I2 $I1) &&
|
|
|
|
I3=$(doit -8 I3 $I2) &&
|
|
|
|
I4=$(doit -7 I4 $I3) &&
|
|
|
|
I5=$(doit -6 I5 $I4) &&
|
|
|
|
I6=$(doit -5 I6 $I5) &&
|
|
|
|
I7=$(doit -4 I7 $I6) &&
|
|
|
|
I8=$(doit -3 I8 $I7) &&
|
|
|
|
IH=$(doit -2 IH $I8) &&
|
|
|
|
|
|
|
|
echo $IH >expected &&
|
|
|
|
git merge-base --independent IB IH >actual &&
|
|
|
|
test_cmp expected actual
|
|
|
|
'
|
|
|
|
|
2008-07-30 10:51:41 +04:00
|
|
|
test_expect_success 'merge-base for octopus-step (setup)' '
|
2010-08-17 10:57:12 +04:00
|
|
|
# Another set to demonstrate base between one commit and a merge
|
|
|
|
# in the documentation.
|
|
|
|
#
|
|
|
|
# * C (MMC) * B (MMB) * A (MMA)
|
|
|
|
# * o * o * o
|
|
|
|
# * o * o * o
|
|
|
|
# * o * o * o
|
|
|
|
# * o | _______/
|
|
|
|
# | |/
|
|
|
|
# | * 1 (MM1)
|
|
|
|
# | _______/
|
|
|
|
# |/
|
|
|
|
# * root (MMR)
|
|
|
|
|
|
|
|
test_commit MMR &&
|
|
|
|
test_commit MM1 &&
|
|
|
|
test_commit MM-o &&
|
|
|
|
test_commit MM-p &&
|
|
|
|
test_commit MM-q &&
|
|
|
|
test_commit MMA &&
|
2008-07-30 10:51:41 +04:00
|
|
|
git checkout MM1 &&
|
2010-08-17 10:57:12 +04:00
|
|
|
test_commit MM-r &&
|
|
|
|
test_commit MM-s &&
|
|
|
|
test_commit MM-t &&
|
|
|
|
test_commit MMB &&
|
2008-07-30 10:51:41 +04:00
|
|
|
git checkout MMR &&
|
2010-08-17 10:57:12 +04:00
|
|
|
test_commit MM-u &&
|
|
|
|
test_commit MM-v &&
|
|
|
|
test_commit MM-w &&
|
|
|
|
test_commit MM-x &&
|
|
|
|
test_commit MMC
|
2008-07-30 10:51:41 +04:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'merge-base A B C' '
|
2010-08-17 10:57:12 +04:00
|
|
|
git rev-parse --verify MM1 >expected &&
|
|
|
|
git rev-parse --verify MMR >expected.sb &&
|
2008-07-30 10:51:41 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
git merge-base --all MMA MMB MMC >actual &&
|
2010-08-17 11:01:15 +04:00
|
|
|
git merge-base --all --octopus MMA MMB MMC >actual.common &&
|
2010-08-17 10:57:12 +04:00
|
|
|
git show-branch --merge-base MMA MMB MMC >actual.sb &&
|
|
|
|
|
|
|
|
test_cmp expected actual &&
|
2010-08-17 11:01:15 +04:00
|
|
|
test_cmp expected.sb actual.common &&
|
2010-08-17 10:57:12 +04:00
|
|
|
test_cmp expected.sb actual.sb
|
2009-08-05 11:59:20 +04:00
|
|
|
'
|
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
test_expect_success 'criss-cross merge-base for octopus-step' '
|
2008-07-30 10:51:41 +04:00
|
|
|
git reset --hard MMR &&
|
2010-08-17 10:57:12 +04:00
|
|
|
test_commit CC1 &&
|
2008-07-30 10:51:41 +04:00
|
|
|
git reset --hard E &&
|
2010-08-17 10:57:12 +04:00
|
|
|
test_commit CC2 &&
|
|
|
|
test_tick &&
|
merge: refuse to create too cool a merge by default
While it makes sense to allow merging unrelated histories of two
projects that started independently into one, in the way "gitk" was
merged to "git" itself aka "the coolest merge ever", such a merge is
still an unusual event. Worse, if somebody creates an independent
history by starting from a tarball of an established project and
sends a pull request to the original project, "git merge" however
happily creates such a merge without any sign of something unusual
is happening.
Teach "git merge" to refuse to create such a merge by default,
unless the user passes a new "--allow-unrelated-histories" option to
tell it that the user is aware that two unrelated projects are
merged.
Because such a "two project merge" is a rare event, a configuration
option to always allow such a merge is not added.
We could add the same option to "git pull" and have it passed
through to underlying "git merge". I do not have a fundamental
opposition against such a feature, but this commit does not do so
and instead leaves it as low-hanging fruit for others, because such
a "two project merge" would be done after fetching the other project
into some location in the working tree of an existing project and
making sure how well they fit together, it is sufficient to allow a
local merge without such an option pass-through from "git pull" to
"git merge". Many tests that are updated by this patch does the
pass-through manually by turning:
git pull something
into its equivalent:
git fetch something &&
git merge --allow-unrelated-histories FETCH_HEAD
If somebody is inclined to add such an option, updated tests in this
change need to be adjusted back to:
git pull --allow-unrelated-histories something
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-03-18 23:21:09 +03:00
|
|
|
# E is a root commit unrelated to MMR root on which CC1 is based
|
|
|
|
git merge -s ours --allow-unrelated-histories CC1 &&
|
2010-08-17 10:57:12 +04:00
|
|
|
test_commit CC-o &&
|
|
|
|
test_commit CCB &&
|
2008-07-30 10:51:41 +04:00
|
|
|
git reset --hard CC1 &&
|
merge: refuse to create too cool a merge by default
While it makes sense to allow merging unrelated histories of two
projects that started independently into one, in the way "gitk" was
merged to "git" itself aka "the coolest merge ever", such a merge is
still an unusual event. Worse, if somebody creates an independent
history by starting from a tarball of an established project and
sends a pull request to the original project, "git merge" however
happily creates such a merge without any sign of something unusual
is happening.
Teach "git merge" to refuse to create such a merge by default,
unless the user passes a new "--allow-unrelated-histories" option to
tell it that the user is aware that two unrelated projects are
merged.
Because such a "two project merge" is a rare event, a configuration
option to always allow such a merge is not added.
We could add the same option to "git pull" and have it passed
through to underlying "git merge". I do not have a fundamental
opposition against such a feature, but this commit does not do so
and instead leaves it as low-hanging fruit for others, because such
a "two project merge" would be done after fetching the other project
into some location in the working tree of an existing project and
making sure how well they fit together, it is sufficient to allow a
local merge without such an option pass-through from "git pull" to
"git merge". Many tests that are updated by this patch does the
pass-through manually by turning:
git pull something
into its equivalent:
git fetch something &&
git merge --allow-unrelated-histories FETCH_HEAD
If somebody is inclined to add such an option, updated tests in this
change need to be adjusted back to:
git pull --allow-unrelated-histories something
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-03-18 23:21:09 +03:00
|
|
|
# E is a root commit unrelated to MMR root on which CC1 is based
|
|
|
|
git merge -s ours --allow-unrelated-histories CC2 &&
|
2010-08-17 10:57:12 +04:00
|
|
|
test_commit CCA &&
|
|
|
|
|
|
|
|
git rev-parse CC1 CC2 >expected &&
|
|
|
|
git merge-base --all CCB CCA^^ CCA^^2 >actual &&
|
2008-07-30 10:51:41 +04:00
|
|
|
|
2010-08-17 10:57:12 +04:00
|
|
|
sort expected >expected.sorted &&
|
|
|
|
sort actual >actual.sorted &&
|
|
|
|
test_cmp expected.sorted actual.sorted
|
2008-07-30 10:51:41 +04:00
|
|
|
'
|
|
|
|
|
merge-base: teach "--fork-point" mode
The "git pull --rebase" command computes the fork point of the
branch being rebased using the reflog entries of the "base" branch
(typically a remote-tracking branch) the branch's work was based on,
in order to cope with the case in which the "base" branch has been
rewound and rebuilt. For example, if the history looked like this:
o---B1
/
---o---o---B2--o---o---o---Base
\
B3
\
Derived
where the current tip of the "base" branch is at Base, but earlier
fetch observed that its tip used to be B3 and then B2 and then B1
before getting to the current commit, and the branch being rebased
on top of the latest "base" is based on commit B3, it tries to find
B3 by going through the output of "git rev-list --reflog base" (i.e.
Base, B1, B2, B3) until it finds a commit that is an ancestor of the
current tip "Derived".
Internally, we have get_merge_bases_many() that can compute this
with one-go. We would want a merge-base between Derived and a
fictitious merge commit that would result by merging all the
historical tips of "base". When such a commit exist, we should get
a single result, which exactly match one of the reflog entries of
"base".
Teach "git merge-base" a new mode, "--fork-point", to compute
exactly that.
Helped-by: Martin von Zweigbergk <martinvonz@gmail.com>
Helped-by: John Keeping <john@keeping.me.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-10-24 03:47:32 +04:00
|
|
|
test_expect_success 'using reflog to find the fork point' '
|
|
|
|
git reset --hard &&
|
|
|
|
git checkout -b base $E &&
|
|
|
|
|
|
|
|
(
|
|
|
|
for count in 1 2 3
|
|
|
|
do
|
|
|
|
git commit --allow-empty -m "Base commit #$count" &&
|
|
|
|
git rev-parse HEAD >expect$count &&
|
|
|
|
git checkout -B derived &&
|
|
|
|
git commit --allow-empty -m "Derived #$count" &&
|
|
|
|
git rev-parse HEAD >derived$count &&
|
|
|
|
git checkout -B base $E || exit 1
|
|
|
|
done
|
|
|
|
|
|
|
|
for count in 1 2 3
|
|
|
|
do
|
|
|
|
git merge-base --fork-point base $(cat derived$count) >actual &&
|
|
|
|
test_cmp expect$count actual || exit 1
|
|
|
|
done
|
|
|
|
|
|
|
|
) &&
|
|
|
|
# check that we correctly default to HEAD
|
|
|
|
git checkout derived &&
|
|
|
|
git merge-base --fork-point base >actual &&
|
|
|
|
test_cmp expect3 actual
|
|
|
|
'
|
|
|
|
|
2016-10-12 23:10:40 +03:00
|
|
|
test_expect_success '--fork-point works with empty reflog' '
|
|
|
|
git -c core.logallrefupdates=false branch no-reflog base &&
|
|
|
|
git merge-base --fork-point no-reflog derived &&
|
|
|
|
test_cmp expect3 actual
|
|
|
|
'
|
|
|
|
|
2013-12-30 23:58:54 +04:00
|
|
|
test_expect_success 'merge-base --octopus --all for complex tree' '
|
|
|
|
# Best common ancestor for JE, JAA and JDD is JC
|
|
|
|
# JE
|
|
|
|
# / |
|
|
|
|
# / |
|
|
|
|
# / |
|
|
|
|
# JAA / |
|
|
|
|
# |\ / |
|
|
|
|
# | \ | JDD |
|
|
|
|
# | \ |/ | |
|
|
|
|
# | JC JD |
|
|
|
|
# | | /| |
|
|
|
|
# | |/ | |
|
|
|
|
# JA | | |
|
|
|
|
# |\ /| | |
|
|
|
|
# X JB | X X
|
|
|
|
# \ \ | / /
|
|
|
|
# \__\|/___/
|
|
|
|
# J
|
|
|
|
test_commit J &&
|
|
|
|
test_commit JB &&
|
|
|
|
git reset --hard J &&
|
|
|
|
test_commit JC &&
|
|
|
|
git reset --hard J &&
|
|
|
|
test_commit JTEMP1 &&
|
|
|
|
test_merge JA JB &&
|
|
|
|
test_merge JAA JC &&
|
|
|
|
git reset --hard J &&
|
|
|
|
test_commit JTEMP2 &&
|
|
|
|
test_merge JD JB &&
|
|
|
|
test_merge JDD JC &&
|
|
|
|
git reset --hard J &&
|
|
|
|
test_commit JTEMP3 &&
|
|
|
|
test_merge JE JC &&
|
|
|
|
git rev-parse JC >expected &&
|
|
|
|
git merge-base --all --octopus JAA JDD JE >actual &&
|
|
|
|
test_cmp expected actual
|
|
|
|
'
|
|
|
|
|
2005-11-11 12:00:52 +03:00
|
|
|
test_done
|