Hi -
On 10/2/20 5:40 PM, René Scharfe wrote:
[snip]
I don't know if these revisions are not ignored due to bugs or because
the feature just isn't strong enough, yet, but I would expect your
particular case to be represented by at least one of these...
Correct.
When skipping a revision, the algorithm attempts to find another
revision that could be responsible for the change. But it might not be
able to find anything. Consider a commit that just adds a few lines to
a file with only 'foo' and 'bar':
commit: "Adding Lines"
-------------
foo
+No commit
+ever touched
+these lines
bar
If we ignored that revision, which commit do we assign those lines to?
If they were "similar" to the existing lines, then the algorithm might
match. But in general, we can't find 'correct' (as defined by a user)
matches for arbitrary changes.
I usually run git with these settings:
[blame]
ignorerevsfile = .git-blame-ignore-revs
markIgnoredLines = true
markUnblamableLines = true
Which points out when --ignore-revs is doing something.
Thanks,
Barret
