From: "Dr. Matthias St. Pierre" <Matthias.St.Pierre@ncp-e.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Stefan Beller <stefanbeller@gmail.com>
Subject: RE: [PATCH] blame: document --color-* options
Date: Wed, 29 Sep 2021 09:19:06 +0000 [thread overview]
Message-ID: <fa7df24dd20e4298883fb038689fff93@ncp-e.com> (raw)
In-Reply-To: <7d2fba09-4898-9b8d-d2c9-89438c8fb2e6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]
> On 28/09/21 19.38, Dr. Matthias St. Pierre wrote:
> > -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.
> > +color.blame.repeated
> > +Use this color to colorize line annotations, if they belong to the same commit
> > +as the preceding line (`git blame --color-lines`). Defaults to cyan.
>
> Why did you change the config name? I think you make mistake here: the
> config name should stay as `color.blame.repeatedLines`.
Yes, you are right. That was not an intended change, the name was truncated accidentally.
Matthias
Dr. Matthias St. Pierre
Tech Lead Cryptography
matthias.st.pierre@ncp-e.com
Phone: +49 911 9968-0
www.ncp-e.com
Headquarters Germany: NCP engineering GmbH • Dombuehler Str. 2 • 90449 • Nuremberg
North American HQ: NCP engineering Inc. • 601 Cleveland Str., Suite 501-25 • Clearwater, FL 33755
Authorized representatives: Peter Soell, Patrick Oliver Graf, Beate Dietrich
Registry Court: Lower District Court of Nuremberg
Commercial register No.: HRB 7786 Nuremberg, VAT identification No.: DE 133557619
This e-mail message including any attachments is for the sole use of the intended recipient(s) and may contain privileged
or confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient,
please immediately contact the sender by reply e-mail and delete the original message and destroy all copies thereof.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7448 bytes --]
next prev parent reply other threads:[~2021-09-29 9:19 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
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 [this message]
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=fa7df24dd20e4298883fb038689fff93@ncp-e.com \
--to=matthias.st.pierre@ncp-e.com \
--cc=bagasdotme@gmail.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.