Re: [PATCH] blame: document actual range specifier behavior

2019-08-09 Thread Junio C Hamano
Junio C Hamano writes: > ... If anything, > perhaps such a description should go to "git help revisions", as it > is not just "blame" but "log". "The dots notation is not about > date-based cutoff, unlike the --since/--until options" is shared by > all history traversal tools. By this, I do not

Re: [PATCH] blame: document actual range specifier behavior

2019-08-08 Thread Junio C Hamano
Daniel Koning writes: > The git-blame(1) man page says that the .. range specifier can be used > to exclude changes "older than" a certain revision. Thanks for spoting a loose-and-colloquial use of "older than" in the doc. As you suspect, the document wanted the phrase to be understood as "reac

[PATCH] blame: document actual range specifier behavior

2019-08-07 Thread Daniel Koning
The git-blame(1) man page says that the .. range specifier can be used to exclude changes "older than" a certain revision. It goes on to say that it collapses all lines "not changed since the range boundary" into the boundary revision. This is the same thing --since= would do, and the man page even