MCPcopy Index your code
hub / github.com/git/git / relevant_commit

Function relevant_commit

revision.c:524–527  ·  view source on GitHub ↗

* A definition of "relevant" commit that we can use to simplify limited graphs * by eliminating side branches. * * A "relevant" commit is one that is !UNINTERESTING (ie we are including it * in our list), or that is a specified BOTTOM commit. Then after computing * a limited list, during processing we can generally ignore boundary merges * coming from outside the graph, (ie from irrelevant p

Source from the content-addressed store, hash-verified

522 * important than Y-X, despite both A and Y being flagged UNINTERESTING.
523 */
524static inline int relevant_commit(struct commit *commit)
525{
526 return (commit->object.flags & (UNINTERESTING | BOTTOM)) != UNINTERESTING;
527}
528
529/*
530 * Return a single relevant commit from a parent list. If we are a TREESAME

Callers 4

one_relevant_parentFunction · 0.85
update_treesameFunction · 0.85
try_to_simplify_commitFunction · 0.85
get_commit_actionFunction · 0.85

Calls

no outgoing calls

Tested by

no test coverage detected