From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
hIpPy <hippy2981@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git alias for options
Date: Fri, 17 Feb 2017 14:31:13 -0800 [thread overview]
Message-ID: <xmqq4lzsqwjy.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170217221317.e5kby2jwutdznnlk@sigill.intra.peff.net> (Jeff King's message of "Fri, 17 Feb 2017 17:13:17 -0500")
Jeff King <peff@peff.net> writes:
> On Fri, Feb 17, 2017 at 11:10:08PM +0100, Ævar Arnfjörð Bjarmason wrote:
>
>> The most gentle first step would be to try to turn the existing config
>> options where you can override cli-options into some declarative thing
>> from the current ad-hoc code we have for each one.
>>
>> That would be no change in behavior, but would make it easier to
>> migrate more things in the future.
>
> Yeah, I'd agree with that. It does not change anything for the users,
> but it makes the implementation less annoying.
Yup, as long as that declarative thing (presumably it would hook
into parse-options that is already sort of declarative) allows some
command line options not overridable with configuration, I think it
would be OK.
I do not think anybody wants to see "reset --hard" and turn it into
"[reset] hard = yes" configuration, and we should not even allow for
that.
next prev parent reply other threads:[~2017-02-17 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 8:23 git alias for options hIpPy
2017-02-17 13:15 ` Michael J Gruber
2017-02-17 13:50 ` Ævar Arnfjörð Bjarmason
2017-02-17 20:42 ` Jeff King
2017-02-17 22:10 ` Ævar Arnfjörð Bjarmason
2017-02-17 22:13 ` Jeff King
2017-02-17 22:31 ` Junio C Hamano [this message]
2017-02-17 22:34 ` hIpPy
2017-02-18 6:33 ` Jeff King
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=xmqq4lzsqwjy.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=hippy2981@gmail.com \
--cc=peff@peff.net \
/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).