From: Junio C Hamano <gitster@pobox.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Dr. Matthias St. Pierre" <Matthias.St.Pierre@ncp-e.com>,
git@vger.kernel.org, Stefan Beller <stefanbeller@gmail.com>
Subject: Re: [PATCH] blame: document --color-* options
Date: Wed, 29 Sep 2021 11:30:56 -0700 [thread overview]
Message-ID: <xmqqk0izdyjj.fsf@gitster.g> (raw)
In-Reply-To: <7745e157-7df9-2da7-f391-8c5bae16f005@gmail.com> (Bagas Sanjaya's message of "Wed, 29 Sep 2021 16:15:55 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> Stefan mentioned "metadata" term to describe the line annotation, from
> commit cdc2d5f11f1a:
>
>> When using git-blame lots of lines contain redundant information, for
>> example in hunks that consist of multiple lines, the metadata (commit
>> name, author, date) are repeated. A reader may not be interested in those,
>> so offer an option to color the information that is repeated from the
>> previous line differently. Traditionally, we use CYAN for lines that
>> are less interesting than others (e.g. hunk header), so go with that.
The documentation is for our end users, who may not have read our
commit log messages, so phrasing that was used in an old commit
message would not help them.
prev parent reply other threads:[~2021-09-29 18:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 19:15 git-blame: '--color-by-age' option not documented in manual page Dr. Matthias St. Pierre
2021-09-25 12:18 ` [PATCH] blame: document --color-* options Bagas Sanjaya
2021-09-25 12:24 ` Bagas Sanjaya
2021-09-27 19:44 ` Junio C Hamano
2021-09-28 5:43 ` Bagas Sanjaya
2021-09-28 12:38 ` Dr. Matthias St. Pierre
2021-09-29 8:01 ` Bagas Sanjaya
2021-09-29 9:19 ` Dr. Matthias St. Pierre
2021-09-29 9:51 ` Bagas Sanjaya
2021-09-29 10:53 ` Dr. Matthias St. Pierre
2021-09-29 11:52 ` Dr. Matthias St. Pierre
2021-09-28 16:22 ` Junio C Hamano
2021-09-29 9:15 ` Bagas Sanjaya
2021-09-29 18:30 ` Junio C Hamano [this message]
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=xmqqk0izdyjj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Matthias.St.Pierre@ncp-e.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=stefanbeller@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 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 NNTP newsgroup(s).