* 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
| 522 | * important than Y-X, despite both A and Y being flagged UNINTERESTING. |
| 523 | */ |
| 524 | static 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 |
no outgoing calls
no test coverage detected