From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 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,RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 46D901FF32 for ; Wed, 18 Oct 2017 00:59:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758707AbdJRAyT (ORCPT ); Tue, 17 Oct 2017 20:54:19 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:53845 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758702AbdJRAyP (ORCPT ); Tue, 17 Oct 2017 20:54:15 -0400 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B7D42A48CA; Tue, 17 Oct 2017 20:54:14 -0400 (EDT) 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=lRoWMt866iJU2dR5GW1FMnbmmak=; b=W2qrd6 jsPk2/wIBznESHtBVEQ+Q4yJMCmBMNTdxcR5MYQAotj0sxt77GCh9oEPoKDu6MGX Ek/1oHuElXYq/nFFQ/zZbejTf5yfYXKz/+HTYVygQghYZt7w98koZlJMq9xrM5vv wpJr1NPXqkP5+EeoTM1Ibk/cP/hnGaFURJO5w= 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=l6K7ImULoxca5xrcZcAwQAHF1McFzY97 ZuXJ7S4le4HUhdNfPKsGLYX8X176H6a4Hs4FBHP0SUDnlYPh8ke2tN84ZhjEMbI2 ySA5+mQJp25LKvapHFveGbEhfgXXW5fT/VPfQSzPHn4kb8wMZH+RWyVZ/6MWfVz2 dgwF4dSmeZg= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id AF63CA48C9; Tue, 17 Oct 2017 20:54:14 -0400 (EDT) Received: from pobox.com (unknown [104.132.0.95]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 2EB57A48C8; Tue, 17 Oct 2017 20:54:14 -0400 (EDT) From: Junio C Hamano To: Marius Paliga Cc: Thais Diniz , Christian Couder , git@vger.kernel.org, Jeff King , Stefan Beller Subject: Re: [PATCH] Added support for new configuration parameter push.pushOption References: Date: Wed, 18 Oct 2017 09:54:12 +0900 In-Reply-To: (Marius Paliga's message of "Tue, 17 Oct 2017 08:32:40 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: DC680C46-B39E-11E7-8362-575F0C78B957-77302942!pb-smtp2.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Marius Paliga writes: > builtin/push.c: add push.pushOption config This is a good title for this change; it would be perfect if it were on the Subject: header ;-) > Currently push options need to be given explicitly, via > the command line as "git push --push-option". > > The UX of Git would be enhanced if push options could be > configured instead of given each time on the command line. > > Add the config option push.pushOption, which is a multi > string option, containing push options that are sent by default. s/Currently p/P/ would be sufficient; we describe the status quo in present tense, and give an order to the codebase to "become like so" (or command a patch monkey to "make the codebase like so") by using imperative mood. I think something shorter like this would be sufficient: Push options need to be given explicitly, via the command line as "git push --push-option