From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCHv2 0/4] blame: (dim rep. metadata lines or fields, decay date coloring)
Date: Thu, 28 Dec 2017 13:03:41 -0800 [thread overview]
Message-ID: <20171228210345.205300-1-sbeller@google.com> (raw)
This is picking up [1], but presenting it in another approach,
as I realized these are orthogonal features:
* dimming repeated lines/fields of information
* giving a quick visual information how old (as a proxy for 'well tested')
a line of code is.
Both features are configurable.
Changes from sending it out in November:
* better commit messages
* rebased on master
Any feedback welcome.
Thanks,
Stefan
[1] https://public-inbox.org/git/20171110011002.10179-1-sbeller@google.com/
Stefan Beller (4):
color.h: document and modernize header
builtin/blame: dim uninteresting metadata
builtin/blame: add option to color metadata fields separately
builtin/blame: highlight recently changed lines
Documentation/config.txt | 23 +++++
builtin/blame.c | 216 ++++++++++++++++++++++++++++++++++++++++++-----
color.c | 2 -
color.h | 49 ++++++++---
t/t8012-blame-colors.sh | 56 ++++++++++++
5 files changed, 311 insertions(+), 35 deletions(-)
create mode 100755 t/t8012-blame-colors.sh
--
2.15.1.620.gb9897f4670-goog
next reply other threads:[~2017-12-28 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 21:03 Stefan Beller [this message]
2017-12-28 21:03 ` [PATCH 1/4] color.h: document and modernize header Stefan Beller
2017-12-28 22:00 ` Eric Sunshine
2018-01-04 19:49 ` Stefan Beller
2017-12-28 21:03 ` [PATCH 2/4] builtin/blame: dim uninteresting metadata Stefan Beller
2017-12-28 22:29 ` Eric Sunshine
2018-01-04 22:10 ` Stefan Beller
2018-01-06 8:26 ` Eric Sunshine
2018-01-08 19:38 ` Stefan Beller
2017-12-28 21:03 ` [PATCH 3/4] builtin/blame: add option to color metadata fields separately Stefan Beller
2017-12-28 21:03 ` [PATCH 4/4] builtin/blame: highlight recently changed lines Stefan Beller
2017-12-28 22:45 ` Eric Sunshine
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171228210345.205300-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).