git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Organov <sorganov@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Aleksey Midenkov <midenok@gmail.com>,
	Abhishek Kumar <abhishekkumar8222@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Git tedious verbosity
Date: Thu, 13 Feb 2020 07:45:45 +0300	[thread overview]
Message-ID: <87sgjf2iyu.fsf@osv.gnss.ru> (raw)
In-Reply-To: <xmqqblq3vhp0.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Wed, 12 Feb 2020 09:28:11 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> Sergey Organov <sorganov@gmail.com> writes:
>
>> It says:
>>
>>    All advice.* variables default to true, and you can tell Git that you
>>    do not need help by setting these to false:
>>
>> If there were an option to set that default to 'false' (advice.default
>> maybe?), it'd have answered the demands of the experts, I think.
>>
>> -- Sergey
>
> This was recently discussed.  A quick search in the list archive
> would have found this thread, for example:
>
>   https://lore.kernel.org/git/xmqqwoa122h1.fsf@gitster-ct.c.googlers.com/

Thanks for pointing! Still ability to configure the default looks both
simpler and more flexible to me.

-- Sergey

  reply	other threads:[~2020-02-13  4:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 21:00 Git tedious verbosity Abhishek Kumar
2020-02-11 14:19 ` Aleksey Midenkov
2020-02-11 19:08   ` Andrew Clayton
2020-02-11 19:55   ` Jeff King
2020-02-11 19:56     ` Jeff King
2020-02-12  4:34       ` Sergey Organov
2020-02-12 17:28         ` Junio C Hamano
2020-02-13  4:45           ` Sergey Organov [this message]
2020-02-12 17:36         ` Junio C Hamano
2020-02-13  4:30           ` Sergey Organov
     [not found] <CAF8BazCScMN1sBspcCycOJBcepbkKfJUvh_hL9MSgNVvs4jKGQ@mail.gmail.com>
2020-02-10 18:49 ` Aleksey Midenkov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgjf2iyu.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=abhishekkumar8222@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=midenok@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.
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 NNTP newsgroup(s).