Commit 991c3dc7 authored by Junio C Hamano's avatar Junio C Hamano

known breakage: revision range computation with clock skew

This is the absolute minimum (and reliable) reproduction recipe
to demonstrate that revision range in a history with clock skew
sometimes fails to mark UNINTERESTING commit in topologically
early parts of the history.

The history looks like this:

	one         four

but one has the largest timestamp.  "git rev-list"
fails to notice that "one" should not be emitted.
Signed-off-by: default avatarJunio C Hamano <[email protected]>
parent 11d54b8b
test_description='properly cull all ancestors'
. ./
commit () {
test_tick &&
echo $1 >file &&
git commit -a -m $1 &&
git tag $1
test_expect_success setup '
touch file &&
git add file &&
commit one &&
test_tick=$(($test_tick - 2400))
commit two &&
commit three &&
commit four &&
git log --pretty=oneline --abbrev-commit
test_expect_failure 'one is ancestor of others and should not be shown' '
git rev-list one --not four >result &&
>expect &&
diff -u expect result
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment