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:30:32 +0300 [thread overview]
Message-ID: <8736bf3y8n.fsf@osv.gnss.ru> (raw)
In-Reply-To: <xmqq7e0rvhau.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Wed, 12 Feb 2020 09:36:41 -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.
>
> Well, just like newbies won't stay to be newbies forever (and that
> is why you can disable advice.frotz once you learned about frotz),
> what you call "experts" won't stay to be experts, either. A new and
> backward incompatible way to work may be introduced and a new advice
> message to guide _everybody_ (including those who thought they were
> already experts) may have to be introduced, and turning off all
> advice.* variables, even the ones that you haven't seen, would hurt
> them.
By "experts" here, in the context of particular discussion, I meant
Linux/UNIX experts who are used to tools being silent, unless verbosity
is explicitly requested (typical --verbose,-v), or at least having a
simple way to make them silent (typical --quiet,-q).
>> So...
So in fact this has little to do with git proficiency.
-- Sergey
next prev parent reply other threads:[~2020-02-13 4:30 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
2020-02-12 17:36 ` Junio C Hamano
2020-02-13 4:30 ` Sergey Organov [this message]
[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
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=8736bf3y8n.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.
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).