From: Patrick Steinhardt Date: Thu, 4 Sep 2025 12:49:56 +0000 (+0200) Subject: revision: drop explicit check for commit graph X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=307e30792b3fb256f58816c4ca67d647eb76c788;p=thirdparty%2Fgit.git revision: drop explicit check for commit graph When filtering down revisions by paths we know to use bloom filters from the commit graph, if we have any. The entry point for this is in `check_maybe_different_in_bloom_filter()`, where we first verify that: - We do have a commit graph. - That the commit is contained therein by checking that we have a proper generation number. - And that the graph contains a bloom filter. The first check is somewhat redundant though: if we don't have a commit graph, then the second check would already tell us that we don't have a generation number for the specific commit. In theory this could be seen as a performance optimization to short-circuit for scenarios where there is no commit graph. But in practice this shouldn't matter: if there is no commit graph, then the commit graph data slab would also be unpopulated and thus a lookup of the commit should happen in constant time. Drop the unnecessary check. Signed-off-by: Patrick Steinhardt Signed-off-by: Junio C Hamano --- diff --git a/revision.c b/revision.c index 6ba8f67054..6018f30a99 100644 --- a/revision.c +++ b/revision.c @@ -774,9 +774,6 @@ static int check_maybe_different_in_bloom_filter(struct rev_info *revs, struct bloom_filter *filter; int result = 0; - if (!revs->repo->objects->commit_graph) - return -1; - if (commit_graph_generation(commit) == GENERATION_NUMBER_INFINITY) return -1;