git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 2/2] blame: document --color-* options

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Oct 1, 2021, 19:10 UTC
Message-ID
<CAPig+cSWutBRQK+Qy=nkaDZRvy4trVNPuo+cF-quC2rBwNe2fw@mail.gmail.com>
In-Reply-To
<20211001113725.13354-3-bagasdotme@gmail.com>
On Fri, Oct 1, 2021 at 7:38 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
Show 14 quoted lines
> Commit cdc2d5f11f1a (builtin/blame: dim uninteresting metadata lines,
> 2018-04-23) and 25d5f52901f0 (builtin/blame: highlight recently changed
> lines, 2018-04-23) introduce --color-lines and --color-by-age options to
> git blame, respectively. While both options are mentioned in usage help,
> they aren't documented in git-blame(1). Document them.
>
> Co-authored-by: Dr. Matthias St. Pierre <m.st.pierre@ncp-e.com>
> Signed-off-by: Dr. Matthias St. Pierre <m.st.pierre@ncp-e.com>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> diff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt
> @@ -136,5 +136,17 @@ take effect.
> +--color-lines::
> +       Color lines differently, if they come from the same commit as the preceding line.
Drop the comma: s/differently,/differently/
> +       This facilitates distinguishing code blocks introduced by different commits.

Taking non-native English speakers into account, perhaps: s/facilitates distinguishing/makes it easier to distinguish/

> +       The color defaults to cyan and be adjusted using the `color.blame.repeatedLines`
s/and be/and can be/
> +       config option. Only the line annotation (see "The Default Format" section)
> +       is colored.
You can drop the last sentence entirely if you start the blurb like this:
    Color line annotations differently, if...
> +--color-by-age::
> +       Color lines depending on the age of the line. The `color.blame.highlightRecent`
> +       config option controls what color is used for which range of age. Only the
> +       line annotation (see "The Default Format" section) is colored.
Ditto about dropping the last sentence.
    Color line annotations depending upon the age of the line.
Show 7 quoted lines
> diff --git a/Documentation/config/color.txt b/Documentation/config/color.txt
> @@ -9,8 +9,8 @@ color.advice.hint::
>  color.blame.highlightRecent::
> -       This can be used to color the metadata of a blame line depending
> -       on age of the line.
> +       Used to color line annotations differently depending on the age of the commit
> +       (`git blame --color-by-age`).
This can be tightened up:
    Specify the line annotation color depending upon the age
    of the commit (`git blame...`).
Show 8 quoted lines
> @@ -20,15 +20,15 @@ before the given timestamp, overwriting older timestamped colors.
>  color.blame.repeatedLines::
> -       Use the customized color for the part of git-blame output that
> -       is repeated meta information per line (such as commit id,
> -       author name, date and timezone). Defaults to cyan.
> +       Use the specified color to colorize line annotations, if they come from the
> +       same commit as the preceding line (`git blame --color-lines`). Defaults to
> +       cyan.
Likewise:
    Specify the line annotation color for lines which
    originate with the same commit (`git blame...`).
Previous: Bagas SanjayaNext: Bagas Sanjaya
Message 5 of 7 in “blame: documentation update”
  1. 0/2 blame: documentation updateBagas Sanjaya, Oct 1, 2021
  2. 1/2 blame: Describe default output formatBagas Sanjaya, Oct 1, 2021
  3. Junio C HamanoOct 1, 2021
  4. 2/2 blame: document --color-* optionsBagas Sanjaya, Oct 1, 2021
  5. Eric SunshineOct 1, 2021
  6. Bagas SanjayaOct 2, 2021
  7. Junio C HamanoOct 4, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.