Thread (8 messages) 8 messages, 4 authors, 2017-10-27

Re: [PATCH] blame: add --fuzzy-lines command line option

From: Junio C Hamano <hidden>
Date: 2017-10-26 06:15:15

Possibly related (same subject, not in this thread)

Isabella Stephens [off-list ref] writes:
If the -L option is used to specify a line range in git blame, and the
end of the range is past the end of the file, git will fail with a fatal
error. It may instead be desirable to perform a git blame for the line
numbers in the intersection of the file and the specified line range.
Even though erroring out upon such input was done as a deliberate
design decision, in retrospect, I do not think the design decision
made much sense.

The code already takes a nonsense input and tries to make best sense
of it, e.g. "-L10,6" is interpreted as "-L6,10" instead of erroring
out.  So if we were to do this kind of change, I suspect that it may
be better to do so unconditionally without introducing a new option.

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help