While `git blame` is able to select interesting line regions of a file, it's not easy to just display blame lines since a recent date, especially for large files. The recent discussion on CMake[1] notes the issue of ensuring any CMake scheme kept up with changes to the fairly long Makefile. This short series first clarifies the marking of 'boundary' commits outwith the revision range or time range, then adds a `--blame-only` option to supress non-blame (boundary) commit lines, with tests, and finally adds tests for the long standing `-b` option that simply blanks out the oid, but still displays the whole file. Philip cc: Sibi Siddharthan <sibisiddharthan.github@xxxxxxxxx> [1] https://lore.kernel.org/git/pull.614.v2.git.1589302254.gitgitgadget@xxxxxxxxx/ Philip Oakley (4): doc: blame: show the boundary commit '^' caret mark blame: add option to show only blamed commits `--blame-only` blame: do not show boundary commits, only those blamed blame: test the -b option, use blank oid for boundary commits. Documentation/blame-options.txt | 4 ++++ Documentation/git-blame.txt | 8 ++++---- builtin/blame.c | 3 +++ t/t8002-blame.sh | 19 +++++++++++++++++++ 4 files changed, 30 insertions(+), 4 deletions(-) -- 2.26.2.windows.1.13.g9dddff6983
