From: Junio C Hamano <gitster@pobox.com>
To: Marius Paliga <marius.paliga@gmail.com>
Cc: <christian.couder@gmail.com>, <git@vger.kernel.org>,
<peff@peff.net>, <sbeller@google.com>,
<thais.dinizbraz@gmail.com>
Subject: Re: [PATCH] builtin/push.c: add push.pushOption config
Date: Tue, 24 Oct 2017 09:59:38 +0900 [thread overview]
Message-ID: <xmqq3769bbt1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171023114449.11902-1-marius.paliga@gmail.com> (Marius Paliga's message of "Mon, 23 Oct 2017 13:44:49 +0200")
Marius Paliga <marius.paliga@gmail.com> writes:
> Push options need to be given explicitly, via the command line as "git
> push --push-option <option>". Add the config option push.pushOption,
> which is a multi-valued option, containing push options that are sent
> by default.
>
> When push options are set in the lower-priority configulation file
> (e.g. /etc/gitconfig, or $HOME/.gitconfig), they can be unset later in
> the more specific repository config by the empty string.
>
> Add tests and update documentation as well.
>
> Signed-off-by: Marius Paliga <marius.paliga@gmail.com>
> ---
Looks good.
> +This is a multi-valued variable, and an empty value can be used in a
> +higher priority cofiguration file (e.g. `.git/config` in a
s/cofig/config/; I think you inherited from me, sorry.
I'll tweak it while queuing; there is not need to resend only to fix
this.
Thanks.
prev parent reply other threads:[~2017-10-24 0:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 6:32 [PATCH] Added support for new configuration parameter push.pushOption Marius Paliga
2017-10-18 0:54 ` Junio C Hamano
2017-10-18 1:04 ` Junio C Hamano
2017-10-19 17:47 ` [PATCH] builtin/push.c: add push.pushOption config Marius Paliga
2017-10-19 19:46 ` Stefan Beller
2017-10-20 2:19 ` Junio C Hamano
2017-10-20 6:17 ` Junio C Hamano
2017-10-20 6:18 ` Junio C Hamano
2017-10-20 8:52 ` Marius Paliga
2017-10-21 1:33 ` Junio C Hamano
2017-10-20 19:02 ` Stefan Beller
2017-10-21 1:52 ` Junio C Hamano
2017-10-23 11:44 ` Marius Paliga
2017-10-24 0:59 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq3769bbt1.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=marius.paliga@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=thais.dinizbraz@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).