2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:48:28
Bo Yang [off-list ref] writes:
Yeah, how do you think use the following syntax: <file1>@<rev1>:<start pos>,<end pos> <file2>@<rev2>:<start pos>,<end pos>
Horrible. That is not how we name things.
What's wrong with bog standard:
$ git log -L 10,20 master -- Documentation/git.txt
which is exactly how "blame" does it?
From: Bo Yang <hidden>
Date: 2016-06-15 22:48:28
Horrible. That is not how we name things. What's wrong with bog standard: $ git log -L 10,20 master -- Documentation/git.txt which is exactly how "blame" does it?
The 'blame' way is very good if we only support one line range. But if we want to support multiple line ranges, I don't think it is suitable for that case. Anyway, how can I specify multi-ranges which refers to multiple files at multiple revision and multiple line ranges using above syntax? Except that, I still can't convince myself that we need multiple ranges support. Anyway, how do we display such a result to our users? Regards! Bo