Re: Seeing which commits modified a range of lines?

[Tom <adatgyujto@gmail.com>]

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> For most backends, such a loop will take forever to terminate 

The termination problem could be mitigated by introducing 
a limit for the search. For example, after going back, say,
10 revisions (or if it's a time limit then after working for,
say, 5 seconds) the loop stops and emacs asks the user if
it should continue working or the user wants to see the 
results up to that point.

If the latter then the user can peruse the results and 
if more info is needed then he can restart the search 
which picks up where it left off using the previously 
collected info and continues working until the limit 
is reached again, etc.

Usually the user looks for some specific change impacting
that code chunk, so there is no need to go back to the 
beginning of time. If the user can control the process
the above described way then he goes back only as far
as needed, so the termination problem may be less of
an issue.