From: Jeff King <peff@peff.net>
To: Aleksey Midenkov <midenok@gmail.com>
Cc: Abhishek Kumar <abhishekkumar8222@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git tedious verbosity
Date: Tue, 11 Feb 2020 14:56:27 -0500 [thread overview]
Message-ID: <20200211195627.GF2127797@coredump.intra.peff.net> (raw)
In-Reply-To: <20200211195549.GE2127797@coredump.intra.peff.net>
On Tue, Feb 11, 2020 at 02:55:49PM -0500, Jeff King wrote:
> On Tue, Feb 11, 2020 at 05:19:53PM +0300, Aleksey Midenkov wrote:
>
> > Nice info, thanks. Does that disable maintenance messages like:
> >
> > Updated 1 path from the index
>
> I don't think it does. Usually how this works is that we add new
> messages which we think might be helpful, enable them by default (since
> users aren't likely to find out about them if they never see them!), and
> then if they turn out to be annoying or verbose, add an advice.* config
> option to allow people to avoid them.
>
> The message quoted above is a relatively new one, and I don't think it's
> hit that third step yet. Patches welcome. :)
Oh, and if you want to see the complete list, look for "advice.*" in
"git help config".
-Peff
next prev parent reply other threads:[~2020-02-11 19:56 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 [this message]
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
[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=20200211195627.GF2127797@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=abhishekkumar8222@gmail.com \
--cc=git@vger.kernel.org \
--cc=midenok@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.
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).