revision: make get_commit_action() a pure predicate#2169
Open
mmontalbo wants to merge 1 commit into
Open
Conversation
mmontalbo
changed the title
mmontalbo
force-pushed
the
mm/line-log-tidy-proto
branch
4 times, most recently
from
July 11, 2026 00:08
3ee39a8 to
80bb64c
Compare
mmontalbo
force-pushed
the
mm/line-log-tidy-proto
branch
from
July 15, 2026 03:59
80bb64c to
5a6705c
Compare
mmontalbo
changed the title
mmontalbo
force-pushed
the
mm/line-log-tidy-proto
branch
from
July 15, 2026 04:21
5a6705c to
6a4fdee
Compare
mmontalbo
marked this pull request as ready for review
July 15, 2026 04:32
mmontalbo
force-pushed
the
mm/line-log-tidy-proto
branch
from
July 15, 2026 17:58
6a4fdee to
5e27e0b
Compare
Author
|
/preview |
|
Preview email sent as pull.2169.git.1784138532955.gitgitgadget@gmail.com |
get_commit_action() reads as a predicate that decides whether a commit is shown or ignored, but for a line-level log without parent rewriting it also calls line_log_process_ranges_arbitrary_commit(), which mutates the tracked line ranges. That hidden side effect makes it unsafe to evaluate ahead of the walk, the way a lookahead would. get_commit_action() was split out of simplify_commit() in beb5af4 (graph API: fix bug in graph_is_interesting(), 2009-08-18) as the show/ignore decision minus the parent rewriting, so the graph renderer could reuse it; line-level log later routed its filtering through it as well, in 3cb9d2b (line-log: more responsive, incremental 'git log -L', 2020-05-11). Besides simplify_commit(), the walk driver, graph_is_interesting() is its only other caller, and it runs only under --graph, which sets rewrite_parents and therefore want_ancestry(); the "-L without ancestry" branch that holds the side effect never fires there, so it is dormant today. The line-level processing folds a commit's tracked ranges onto its parents, which must happen even for a commit that get_commit_action() filters from the output, or the ranges never reach the parents. Move it to simplify_commit() and run it before get_commit_action(), gated by get_commit_action()'s leading checks (already shown, uninteresting, and the like) so a commit ignored by those is not folded, as before; factor those checks out as commit_early_ignore(). get_commit_action() is then side-effect free. commit_early_ignore() runs twice on the -L path, once for that gate and once inside get_commit_action(), but it reads only object flags and pack membership, disjoint from the TREESAME flag the fold sets, so the repeat is harmless. Add a "line-log-peek" subcommand to the revision-walking test helper that evaluates get_commit_action() on a commit the walk has not reached yet, plus a t4211 check that the call leaves the commit's flags unchanged. The flags are compared rather than the commit list because add_line_range() merges ranges by union, which is idempotent, so the side effect never changed which commits a linear -L history shows. Suggested-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Michael Montalbo <mmontalbo@gmail.com>
mmontalbo
force-pushed
the
mm/line-log-tidy-proto
branch
from
July 15, 2026 18:04
5e27e0b to
7dd9136
Compare
Author
|
/submit |
|
Submitted as pull.2169.git.1784143793613.gitgitgadget@gmail.com To fetch this version into To fetch this version to local tag |
|
This branch is now known as |
|
This patch series was integrated into seen via git@ee63858. |
|
There was a status update in the "New Topics" section about the branch The 'get_commit_action()' function has been refactored to be a pure predicate by moving the side-effecting line-level log range folding to 'simplify_commit()'. This ensures that evaluating a commit's action before the walk reaches it does not prematurely mutate its tracked line ranges, making it safer for potential lookahead evaluations. Needs review. source: <pull.2169.git.1784143793613.gitgitgadget@gmail.com> |
|
There was a status update in the "Cooking" section about the branch The 'get_commit_action()' function has been refactored to be a pure predicate by moving the side-effecting line-level log range folding to 'simplify_commit()'. This ensures that evaluating a commit's action before the walk reaches it does not prematurely mutate its tracked line ranges, making it safer for potential lookahead evaluations. Needs review. source: <pull.2169.git.1784143793613.gitgitgadget@gmail.com> |
|
There was a status update in the "Cooking" section about the branch The 'get_commit_action()' function has been refactored to be a pure predicate by moving the side-effecting line-level log range folding to 'simplify_commit()'. This ensures that evaluating a commit's action before the walk reaches it does not prematurely mutate its tracked line ranges, making it safer for potential lookahead evaluations. Needs review. source: <pull.2169.git.1784143793613.gitgitgadget@gmail.com> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cc: SZEDER Gábor szeder.dev@gmail.com