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-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,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 92C171F4B4 for ; Mon, 28 Sep 2020 18:46:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726636AbgI1SqQ (ORCPT ); Mon, 28 Sep 2020 14:46:16 -0400 Received: from pb-smtp21.pobox.com ([173.228.157.53]:55260 "EHLO pb-smtp21.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726424AbgI1SqQ (ORCPT ); Mon, 28 Sep 2020 14:46:16 -0400 Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id D026CED999; Mon, 28 Sep 2020 14:46:15 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=7/QUB1UCnEbQt0WBjHcMXCnY360=; b=fHoez7 uWMBO/7F78PrSMxRsxTtd7hItFqYYO9opXu9a0q/R/DkDdtIqUoTJNrc7qf5Zpbj h3mRAf5+f4fqI4t/e7iRC3VOr259InlVF/uoIa/e5zv7aiFUO+1H5jP5ESOHauc4 VHXt++6oWx3RU9WhXf6k9hwVPCD+9c9YXqTZY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=au2qaBswSP6mXSFOLr5/HZJXIZy78k9s 5TM1hOumSLXEgpu0VKkFvFzNx7mPW3HSKoODq3pCVLj3H86rai7Df2r3lmUrI6z+ lyjvLMMQTy93WPNvtPTK1CPojNOlTvfJ6hQcH3iW5jkVGWSM5Fjaf8JQg/WOsDYo 0S/cutZz3PU= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id C7BA9ED995; Mon, 28 Sep 2020 14:46:15 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.74.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 16596ED994; Mon, 28 Sep 2020 14:46:13 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Evan Grim Cc: git@vger.kernel.org Subject: Re: git commit-tree does not honor commit.gpgSign config References: Date: Mon, 28 Sep 2020 11:46:11 -0700 In-Reply-To: (Evan Grim's message of "Mon, 28 Sep 2020 10:21:42 -0600") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: E1EFD9C4-01BA-11EB-9A7B-843F439F7C89-77302942!pb-smtp21.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Evan Grim writes: > Is it a bug that `git-commit-tree` doesn't honor the `commit.gpgSign` > configuration option? It would be a bug if it did, as a low level plumbing tool to build scripts around, it would not want its behaviour to be affected by end-user configuration (rather, scripts that are written using these plumbing command do want to handle end-user customization their own ways).