revision: --ancestry-path
"rev-list A..H" computes the set of commits that are ancestors of H, but
excludes the ones that are ancestors of A. This is useful to see what
happened to the history leading to H since A, in the sense that "what does
H have that did not exist in A" (e.g. when you have a choice to update to
H from A).
x---x---A---B---C <-- topic
/ \
x---x---x---o---o---o---o---M---D---E---F---G <-- dev
/ \
x---o---o---o---o---o---o---o---o---o---o---o---N---H <-- master
The result in the above example would be the commits marked with caps
letters (except for A itself, of course), and the ones marked with 'o'.
When you want to find out what commits in H are contaminated with the bug
introduced by A and need fixing, however, you might want to view only the
subset of "A..B" that are actually descendants of A, i.e. excluding the
ones marked with 'o'. Introduce a new option --ancestry-path to compute
this set with "rev-list --ancestry-path A..B".
Note that in practice, you would build a fix immediately on top of A and
"git branch --contains A" will give the names of branches that you would
need to merge the fix into (i.e. topic, dev and master), so this may not
be worth paying the extra cost of postprocessing.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-04-20 22:48:39 +02:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='--ancestry-path'
|
|
|
|
|
|
|
|
# D---E-------F
|
|
|
|
# / \ \
|
|
|
|
# B---C---G---H---I---J
|
|
|
|
# / \
|
|
|
|
# A-------K---------------L--M
|
|
|
|
#
|
2022-08-19 06:28:10 +02:00
|
|
|
# D..M == E F G H I J K L M
|
|
|
|
# --ancestry-path D..M == E F H I J L M
|
|
|
|
# --ancestry-path=F D..M == E F J L M
|
|
|
|
# --ancestry-path=G D..M == G H I J L M
|
|
|
|
# --ancestry-path=H D..M == E G H I J L M
|
|
|
|
# --ancestry-path=K D..M == K L M
|
|
|
|
# --ancestry-path=K --ancestry-path=F D..M == E F J K L M
|
2010-06-04 01:17:37 +02:00
|
|
|
#
|
|
|
|
# D..M -- M.t == M
|
|
|
|
# --ancestry-path D..M -- M.t == M
|
2013-05-13 17:00:46 +02:00
|
|
|
#
|
|
|
|
# F...I == F G H I
|
|
|
|
# --ancestry-path F...I == F H I
|
2013-05-16 17:32:28 +02:00
|
|
|
#
|
|
|
|
# G..M -- G.t == [nothing - was dropped in "-s ours" merge L]
|
2013-05-16 17:32:39 +02:00
|
|
|
# --ancestry-path G..M -- G.t == L
|
|
|
|
# --ancestry-path --simplify-merges G^..M -- G.t == G L
|
revision: --ancestry-path
"rev-list A..H" computes the set of commits that are ancestors of H, but
excludes the ones that are ancestors of A. This is useful to see what
happened to the history leading to H since A, in the sense that "what does
H have that did not exist in A" (e.g. when you have a choice to update to
H from A).
x---x---A---B---C <-- topic
/ \
x---x---x---o---o---o---o---M---D---E---F---G <-- dev
/ \
x---o---o---o---o---o---o---o---o---o---o---o---N---H <-- master
The result in the above example would be the commits marked with caps
letters (except for A itself, of course), and the ones marked with 'o'.
When you want to find out what commits in H are contaminated with the bug
introduced by A and need fixing, however, you might want to view only the
subset of "A..B" that are actually descendants of A, i.e. excluding the
ones marked with 'o'. Introduce a new option --ancestry-path to compute
this set with "rev-list --ancestry-path A..B".
Note that in practice, you would build a fix immediately on top of A and
"git branch --contains A" will give the names of branches that you would
need to merge the fix into (i.e. topic, dev and master), so this may not
be worth paying the extra cost of postprocessing.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-04-20 22:48:39 +02:00
|
|
|
|
2020-11-19 00:44:36 +01:00
|
|
|
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main
|
tests: mark tests relying on the current default for `init.defaultBranch`
In addition to the manual adjustment to let the `linux-gcc` CI job run
the test suite with `master` and then with `main`, this patch makes sure
that GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME is set in all test scripts
that currently rely on the initial branch name being `master by default.
To determine which test scripts to mark up, the first step was to
force-set the default branch name to `master` in
- all test scripts that contain the keyword `master`,
- t4211, which expects `t/t4211/history.export` with a hard-coded ref to
initialize the default branch,
- t5560 because it sources `t/t556x_common` which uses `master`,
- t8002 and t8012 because both source `t/annotate-tests.sh` which also
uses `master`)
This trick was performed by this command:
$ sed -i '/^ *\. \.\/\(test-lib\|lib-\(bash\|cvs\|git-svn\)\|gitweb-lib\)\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' $(git grep -l master t/t[0-9]*.sh) \
t/t4211*.sh t/t5560*.sh t/t8002*.sh t/t8012*.sh
After that, careful, manual inspection revealed that some of the test
scripts containing the needle `master` do not actually rely on a
specific default branch name: either they mention `master` only in a
comment, or they initialize that branch specificially, or they do not
actually refer to the current default branch. Therefore, the
aforementioned modification was undone in those test scripts thusly:
$ git checkout HEAD -- \
t/t0027-auto-crlf.sh t/t0060-path-utils.sh \
t/t1011-read-tree-sparse-checkout.sh \
t/t1305-config-include.sh t/t1309-early-config.sh \
t/t1402-check-ref-format.sh t/t1450-fsck.sh \
t/t2024-checkout-dwim.sh \
t/t2106-update-index-assume-unchanged.sh \
t/t3040-subprojects-basic.sh t/t3301-notes.sh \
t/t3308-notes-merge.sh t/t3423-rebase-reword.sh \
t/t3436-rebase-more-options.sh \
t/t4015-diff-whitespace.sh t/t4257-am-interactive.sh \
t/t5323-pack-redundant.sh t/t5401-update-hooks.sh \
t/t5511-refspec.sh t/t5526-fetch-submodules.sh \
t/t5529-push-errors.sh t/t5530-upload-pack-error.sh \
t/t5548-push-porcelain.sh \
t/t5552-skipping-fetch-negotiator.sh \
t/t5572-pull-submodule.sh t/t5608-clone-2gb.sh \
t/t5614-clone-submodules-shallow.sh \
t/t7508-status.sh t/t7606-merge-custom.sh \
t/t9302-fast-import-unpack-limit.sh
We excluded one set of test scripts in these commands, though: the range
of `git p4` tests. The reason? `git p4` stores the (foreign) remote
branch in the branch called `p4/master`, which is obviously not the
default branch. Manual analysis revealed that only five of these tests
actually require a specific default branch name to pass; They were
modified thusly:
$ sed -i '/^ *\. \.\/lib-git-p4\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' t/t980[0167]*.sh t/t9811*.sh
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-11-19 00:44:19 +01:00
|
|
|
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME
|
|
|
|
|
revision: --ancestry-path
"rev-list A..H" computes the set of commits that are ancestors of H, but
excludes the ones that are ancestors of A. This is useful to see what
happened to the history leading to H since A, in the sense that "what does
H have that did not exist in A" (e.g. when you have a choice to update to
H from A).
x---x---A---B---C <-- topic
/ \
x---x---x---o---o---o---o---M---D---E---F---G <-- dev
/ \
x---o---o---o---o---o---o---o---o---o---o---o---N---H <-- master
The result in the above example would be the commits marked with caps
letters (except for A itself, of course), and the ones marked with 'o'.
When you want to find out what commits in H are contaminated with the bug
introduced by A and need fixing, however, you might want to view only the
subset of "A..B" that are actually descendants of A, i.e. excluding the
ones marked with 'o'. Introduce a new option --ancestry-path to compute
this set with "rev-list --ancestry-path A..B".
Note that in practice, you would build a fix immediately on top of A and
"git branch --contains A" will give the names of branches that you would
need to merge the fix into (i.e. topic, dev and master), so this may not
be worth paying the extra cost of postprocessing.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-04-20 22:48:39 +02:00
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
test_merge () {
|
|
|
|
test_tick &&
|
|
|
|
git merge -s ours -m "$2" "$1" &&
|
|
|
|
git tag "$2"
|
|
|
|
}
|
|
|
|
|
|
|
|
test_expect_success setup '
|
|
|
|
test_commit A &&
|
|
|
|
test_commit B &&
|
|
|
|
test_commit C &&
|
|
|
|
test_commit D &&
|
|
|
|
test_commit E &&
|
|
|
|
test_commit F &&
|
|
|
|
git reset --hard C &&
|
|
|
|
test_commit G &&
|
|
|
|
test_merge E H &&
|
|
|
|
test_commit I &&
|
|
|
|
test_merge F J &&
|
|
|
|
git reset --hard A &&
|
|
|
|
test_commit K &&
|
|
|
|
test_merge J L &&
|
|
|
|
test_commit M
|
|
|
|
'
|
|
|
|
|
2022-08-19 06:28:09 +02:00
|
|
|
test_ancestry () {
|
|
|
|
args=$1
|
|
|
|
expected=$2
|
|
|
|
test_expect_success "log $args" "
|
|
|
|
test_write_lines $expected >expect &&
|
|
|
|
git log --format=%s $args >raw &&
|
|
|
|
|
|
|
|
if test -n \"$expected\"
|
|
|
|
then
|
|
|
|
sort raw >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
else
|
|
|
|
test_must_be_empty raw
|
|
|
|
fi
|
|
|
|
"
|
|
|
|
}
|
2010-06-04 01:17:37 +02:00
|
|
|
|
2022-08-19 06:28:09 +02:00
|
|
|
test_ancestry "D..M" "E F G H I J K L M"
|
2013-05-13 17:00:46 +02:00
|
|
|
|
2022-08-19 06:28:09 +02:00
|
|
|
test_ancestry "--ancestry-path D..M" "E F H I J L M"
|
2022-08-19 06:28:10 +02:00
|
|
|
test_ancestry "--ancestry-path=F D..M" "E F J L M"
|
|
|
|
test_ancestry "--ancestry-path=G D..M" "G H I J L M"
|
|
|
|
test_ancestry "--ancestry-path=H D..M" "E G H I J L M"
|
|
|
|
test_ancestry "--ancestry-path=K D..M" "K L M"
|
|
|
|
test_ancestry "--ancestry-path=F --ancestry-path=K D..M" "E F J K L M"
|
2013-05-13 17:00:46 +02:00
|
|
|
|
2022-08-19 06:28:09 +02:00
|
|
|
test_ancestry "D..M -- M.t" "M"
|
|
|
|
test_ancestry "--ancestry-path D..M -- M.t" "M"
|
2013-05-16 17:32:28 +02:00
|
|
|
|
2022-08-19 06:28:09 +02:00
|
|
|
test_ancestry "F...I" "F G H I"
|
|
|
|
test_ancestry "--ancestry-path F...I" "F H I"
|
2013-05-16 17:32:39 +02:00
|
|
|
|
2022-08-19 06:28:09 +02:00
|
|
|
test_ancestry "G..M -- G.t" ""
|
|
|
|
test_ancestry "--ancestry-path G..M -- G.t" "L"
|
|
|
|
test_ancestry "--ancestry-path --simplify-merges G^..M -- G.t" "G L"
|
2013-05-16 17:32:28 +02:00
|
|
|
|
2011-08-25 18:49:13 +02:00
|
|
|
# b---bc
|
|
|
|
# / \ /
|
|
|
|
# a X
|
|
|
|
# \ / \
|
|
|
|
# c---cb
|
2011-09-15 10:34:31 +02:00
|
|
|
#
|
|
|
|
# All refnames prefixed with 'x' to avoid confusion with the tags
|
|
|
|
# generated by test_commit on case-insensitive systems.
|
2011-08-25 18:49:13 +02:00
|
|
|
test_expect_success 'setup criss-cross' '
|
|
|
|
mkdir criss-cross &&
|
|
|
|
(cd criss-cross &&
|
|
|
|
git init &&
|
|
|
|
test_commit A &&
|
2020-11-19 00:44:36 +01:00
|
|
|
git checkout -b xb main &&
|
2011-08-25 18:49:13 +02:00
|
|
|
test_commit B &&
|
2020-11-19 00:44:36 +01:00
|
|
|
git checkout -b xc main &&
|
2011-08-25 18:49:13 +02:00
|
|
|
test_commit C &&
|
2011-09-15 10:34:31 +02:00
|
|
|
git checkout -b xbc xb -- &&
|
|
|
|
git merge xc &&
|
|
|
|
git checkout -b xcb xc -- &&
|
|
|
|
git merge xb &&
|
2020-11-19 00:44:36 +01:00
|
|
|
git checkout main)
|
2011-08-25 18:49:13 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
# no commits in bc descend from cb
|
|
|
|
test_expect_success 'criss-cross: rev-list --ancestry-path cb..bc' '
|
|
|
|
(cd criss-cross &&
|
2011-09-15 10:34:31 +02:00
|
|
|
git rev-list --ancestry-path xcb..xbc > actual &&
|
2019-11-26 20:46:07 +01:00
|
|
|
test_must_be_empty actual)
|
2011-08-25 18:49:13 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
# no commits in repository descend from cb
|
2011-08-26 02:51:50 +02:00
|
|
|
test_expect_success 'criss-cross: rev-list --ancestry-path --all ^cb' '
|
2011-08-25 18:49:13 +02:00
|
|
|
(cd criss-cross &&
|
2011-09-15 10:34:31 +02:00
|
|
|
git rev-list --ancestry-path --all ^xcb > actual &&
|
2019-11-26 20:46:07 +01:00
|
|
|
test_must_be_empty actual)
|
2011-08-25 18:49:13 +02:00
|
|
|
'
|
|
|
|
|
revision: --ancestry-path
"rev-list A..H" computes the set of commits that are ancestors of H, but
excludes the ones that are ancestors of A. This is useful to see what
happened to the history leading to H since A, in the sense that "what does
H have that did not exist in A" (e.g. when you have a choice to update to
H from A).
x---x---A---B---C <-- topic
/ \
x---x---x---o---o---o---o---M---D---E---F---G <-- dev
/ \
x---o---o---o---o---o---o---o---o---o---o---o---N---H <-- master
The result in the above example would be the commits marked with caps
letters (except for A itself, of course), and the ones marked with 'o'.
When you want to find out what commits in H are contaminated with the bug
introduced by A and need fixing, however, you might want to view only the
subset of "A..B" that are actually descendants of A, i.e. excluding the
ones marked with 'o'. Introduce a new option --ancestry-path to compute
this set with "rev-list --ancestry-path A..B".
Note that in practice, you would build a fix immediately on top of A and
"git branch --contains A" will give the names of branches that you would
need to merge the fix into (i.e. topic, dev and master), so this may not
be worth paying the extra cost of postprocessing.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-04-20 22:48:39 +02:00
|
|
|
test_done
|