From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 5ED131F8C8 for ; Wed, 29 Sep 2021 18:31:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346207AbhI2Sck (ORCPT ); Wed, 29 Sep 2021 14:32:40 -0400 Received: from pb-smtp1.pobox.com ([64.147.108.70]:65362 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346192AbhI2Sck (ORCPT ); Wed, 29 Sep 2021 14:32:40 -0400 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 5DE6FE95C2; Wed, 29 Sep 2021 14:30:58 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=t7Vl1hus8BObGCABC2MaDWyEWYrwO88gwDvdtI Nvdjc=; b=I213Vj9vQAfx9aGsEoIRec8JjzMKwghzAeiLJtrfAXdvPM/GrzL5Ag FnL3tDiHEw1KE0HlR0XjjjbYgegSPHxn3vPnmkEwBKfb7x1a9CtrbdaFTg7NSkA8 6xasr5UJVQrx8uUWPMpDHzPsPMyFDIDOqdN1u6WlwTKlo8NVFfl0c= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 561F0E95C1; Wed, 29 Sep 2021 14:30:58 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [104.133.2.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id B8519E95BF; Wed, 29 Sep 2021 14:30:57 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Bagas Sanjaya Cc: "Dr. Matthias St. Pierre" , git@vger.kernel.org, Stefan Beller Subject: Re: [PATCH] blame: document --color-* options References: <20210925121817.1089897-1-bagasdotme@gmail.com> <7745e157-7df9-2da7-f391-8c5bae16f005@gmail.com> Date: Wed, 29 Sep 2021 11:30:56 -0700 In-Reply-To: <7745e157-7df9-2da7-f391-8c5bae16f005@gmail.com> (Bagas Sanjaya's message of "Wed, 29 Sep 2021 16:15:55 +0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 638B9172-2153-11EC-97A7-62A2C8D8090B-77302942!pb-smtp1.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Bagas Sanjaya writes: > Stefan mentioned "metadata" term to describe the line annotation, from > commit cdc2d5f11f1a: > >> When using git-blame lots of lines contain redundant information, for >> example in hunks that consist of multiple lines, the metadata (commit >> name, author, date) are repeated. A reader may not be interested in those, >> so offer an option to color the information that is repeated from the >> previous line differently. Traditionally, we use CYAN for lines that >> are less interesting than others (e.g. hunk header), so go with that. The documentation is for our end users, who may not have read our commit log messages, so phrasing that was used in an old commit message would not help them.