aboutsummaryrefslogtreecommitdiff
path: root/shallow.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2022-02-17 16:25:05 -0800
committerJunio C Hamano <gitster@pobox.com>2022-02-17 16:25:05 -0800
commit708cbef33a2c905c920e94b70d0946f9f4ff3a4e (patch)
tree97c45e78e356cdfc71deb5f57499d3e2f5e8ae45 /shallow.c
parentd077db1df0aef3db479904429e8008d8fc0e3fb3 (diff)
parent9d505b7b49c00c5fa99a25506e63a2ef326a0062 (diff)
downloadgit-708cbef33a2c905c920e94b70d0946f9f4ff3a4e.tar.xz
Merge branch 'jz/rev-list-exclude-first-parent-only'
"git log" and friends learned an option --exclude-first-parent-only to propagate UNINTERESTING bit down only along the first-parent chain, just like --first-parent option shows commits that lack the UNINTERESTING bit only along the first-parent chain. * jz/rev-list-exclude-first-parent-only: git-rev-list: add --exclude-first-parent-only flag
Diffstat (limited to 'shallow.c')
-rw-r--r--shallow.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/shallow.c b/shallow.c
index 9ed18eb884..71e5876f37 100644
--- a/shallow.c
+++ b/shallow.c
@@ -603,7 +603,7 @@ static int mark_uninteresting(const char *refname, const struct object_id *oid,
if (!commit)
return 0;
commit->object.flags |= UNINTERESTING;
- mark_parents_uninteresting(commit);
+ mark_parents_uninteresting(NULL, commit);
return 0;
}