All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 27 Sep 2021 12:44:14 -0700	[thread overview]
Message-ID: <xmqq5yulregh.fsf@gitster.g> (raw)
In-Reply-To: <20210925121817.1089897-1-bagasdotme@gmail.com> (Bagas Sanjaya's message of "Sat, 25 Sep 2021 19:18:18 +0700")

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> diff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt
> index 117f4cf806..b15999a3c8 100644
> --- a/Documentation/blame-options.txt
> +++ b/Documentation/blame-options.txt
> @@ -136,5 +136,13 @@ take effect.
>  	option.  An empty file name, `""`, will clear the list of revs from
>  	previously processed files.
>  
> +--color-lines::
> +	Color lines that contain repeated metadata. The color used is set with
> +	`color.blame.repeatedLines` config option.
> +
> +--color-by-age::
> +	Color metadata depending on age of the line. `color.blame.highlightRecent`
> +	config option controls what color is used for each range of age.

Nowhere in "git blame --help" output we mention anything about
"metadata", so the readers of this new description will be left
puzzled what the word means in the context of this command.

We would need to pick words or phrases that readers can link easily
with the description of "THE PORCELAIN FORMAT" section.

Thanks.

  parent reply	other threads:[~2021-09-27 19:44 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 [this message]
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

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=xmqq5yulregh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.