git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert Estelle via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Robert Estelle <robert.estelle@gmail.com>,
	Robert Estelle <robertestelle@gmail.com>
Subject: [PATCH 2/3] blame: document --color-{lines,by-age} config
Date: Thu, 02 Feb 2023 19:16:45 +0000	[thread overview]
Message-ID: <6b0bf073cf0e06e4cfe51f4c10f632344c163921.1675365406.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1449.git.git.1675365406.gitgitgadget@gmail.com>

From: Robert Estelle <robertestelle@gmail.com>

These flags correspond to specific values of the `blame.coloring` config
option. This adds a small note mentioning this correspondence.

Signed-off-by: Robert Estelle <robertestelle@gmail.com>
---
 Documentation/blame-options.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt
index 9a663535f44..170016c941e 100644
--- a/Documentation/blame-options.txt
+++ b/Documentation/blame-options.txt
@@ -141,11 +141,15 @@ take effect.
 	the same commit as the preceding line. This makes it easier to distinguish
 	code blocks introduced by different commits. The color defaults to cyan and
 	can be adjusted using the `color.blame.repeatedLines` config option.
+	It corresponds to the value `repeatedLines` in the `blame.coloring`
+	configuration setting in linkgit:git-config[1] .
 
 --color-by-age::
 	Color line annotations depending on the age of the line in the default format.
 	The `color.blame.highlightRecent` config option controls what color is used for
 	each range of age.
+	It corresponds to the value `highlightRecent` in the `blame.coloring`
+	configuration setting in linkgit:git-config[1] .
 
 -h::
 	Show help message.
-- 
gitgitgadget


  parent reply	other threads:[~2023-02-02 19:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 19:16 [PATCH 0/3] blame: allow blame.coloring to specify both --color-lines and --color-by-age Robert Estelle via GitGitGadget
2023-02-02 19:16 ` [PATCH 1/3] blame: add test for --color-lines + --color-by-age Robert Estelle via GitGitGadget
2023-02-02 19:16 ` Robert Estelle via GitGitGadget [this message]
2023-02-02 19:16 ` [PATCH 3/3] blame: support multiple values in blame.coloring Robert Estelle via GitGitGadget

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=6b0bf073cf0e06e4cfe51f4c10f632344c163921.1675365406.git.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=robert.estelle@gmail.com \
    --cc=robertestelle@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).