From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Wed, 29 Sep 2021 09:15:55 GMT
Subject: Re: [PATCH] blame: document --color-* options
Message-ID: <7745e157-7df9-2da7-f391-8c5bae16f005@gmail.com>
In-Reply-To: <xmqq4ka4n00h.fsf@gitster.g>

On 28/09/21 23.22, Junio C Hamano wrote:
> Sorry for skipping a level of logical progression in the suggestion.
> 
> While I do not think we want to add another section for the default
> format, if we were to add such a section, the new description should
> use phrases that would have been used, and such a section would not
> use a new and unclear "metadata" in the description.  Instead it
> would use phrases that the users can look for elsewhere in the same
> documentation.
> 
> What is colored is the summary of the commit the line came from
> (abbreviated commit object name, plus the author name and time by
> default) plus the line number, I think.
> 
> Thanks.
> 

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.


-- 
An old man doll... just what I always wanted! - Clara