From: Philip Oakley <philipoakley@iee.email>
To: git@vger.kernel.org
Cc: Sibi Siddharthan <sibisiddharthan.github@gmail.com>
Subject: [PATCH 0/4] Selectively show only blamed limes
Date: Mon, 25 May 2020 22:57:47 +0100 [thread overview]
Message-ID: <20200525215751.1735-1-philipoakley@iee.email> (raw)
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@gmail.com>
[1] https://lore.kernel.org/git/pull.614.v2.git.1589302254.gitgitgadget@gmail.com/
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
next reply other threads:[~2020-05-25 21:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 21:57 Philip Oakley [this message]
2020-05-25 21:57 ` [PATCH 1/4] doc: blame: show the boundary commit '^' caret mark Philip Oakley
2020-05-25 21:57 ` [PATCH 2/4] blame: add option to show only blamed commits `--blame-only` Philip Oakley
2020-05-25 21:57 ` [PATCH 3/4] blame: do not show boundary commits, only those blamed Philip Oakley
2020-05-25 21:57 ` [PATCH 4/4] blame: test the -b option, use blank oid for boundary commits Philip Oakley
2020-05-27 7:30 ` Jeff King
2020-05-27 10:52 ` Philip Oakley
2020-05-27 7:23 ` [PATCH 0/4] Selectively show only blamed limes Jeff King
2020-05-27 10:24 ` Philip Oakley
2020-05-28 16:45 ` Jeff King
2020-05-28 18:30 ` Junio C Hamano
2020-05-30 16:18 ` Philip Oakley
2020-05-31 16:02 ` Junio C Hamano
2020-05-31 16:28 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200525215751.1735-1-philipoakley@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=sibisiddharthan.github@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.