Re: Finding all commits which modify a file
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:52:51
Santi Béjar [off-list ref] writes:
quoted hunk
diff --git a/revision.c b/revision.c index 064e351..db97250 100644 --- a/revision.c +++ b/revision.c@@ -492,7 +492,7 @@ static void try_to_simplify_commit(struct rev_info*revs, struct commit *commit) } die("bad tree compare for commit %s", sha1_to_hex(commit->object.sha1)); } - if (tree_changed && !tree_same) + if ((tree_changed && !tree_same) || (!revs->simplify_history && tree_changed))
Is that the same as saying this? if (!(tree_same && revs->simplify_history) && tree_changed) return; Which reads: unless we find a parent that matches the result and we are simplifying the history, a child different from at least one parent is worth showing. Which makes sort of sense at the conceptual level, but I am not sure if it is practically useful (the same issue with --full-history that makes complex history almost unreadable).