Skip to content

Commit d5a6f50

Browse files
pks-tgitster
authored andcommitted
blame: drop explicit check for commit graph
Our blaming subsystem knows to use bloom filters from commit graphs to speed up the whole computation. The setup of this happens in `setup_blame_bloom_data()`, where we first verify that we even have a commit graph in the first place. This check is redundant though, as we call `get_bloom_filter_settings()` immediately afterwards which, which already knows to return a `NULL` pointer in case we don't have a commit graph. Drop the redundant check. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 2462961 commit d5a6f50

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

blame.c

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2909,9 +2909,6 @@ void setup_blame_bloom_data(struct blame_scoreboard *sb)
29092909
struct blame_bloom_data *bd;
29102910
struct bloom_filter_settings *bs;
29112911

2912-
if (!sb->repo->objects->commit_graph)
2913-
return;
2914-
29152912
bs = get_bloom_filter_settings(sb->repo);
29162913
if (!bs)
29172914
return;

0 commit comments

Comments
 (0)