From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Dr. Matthias St. Pierre" <Matthias.St.Pierre@ncp-e.com>
Cc: git@vger.kernel.org, Stefan Beller <stefanbeller@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] blame: document --color-* options
Date: Sat, 25 Sep 2021 19:24:51 +0700 [thread overview]
Message-ID: <355a8c33-2063-80be-ae88-515daefef8c4@gmail.com> (raw)
In-Reply-To: <20210925121817.1089897-1-bagasdotme@gmail.com>
On 25/09/21 19.18, Bagas Sanjaya wrote:
> 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.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Oops, I forgot Reported-by trailer.
Reported-by: Dr. Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-09-25 12:24 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 [this message]
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
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=355a8c33-2063-80be-ae88-515daefef8c4@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Matthias.St.Pierre@ncp-e.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.