From: Junio C Hamano <gitster@pobox.com>
To: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes.Schindelin@gmx.de, ps@pks.im,
james@jamesliu.io, Jeff King <peff@peff.net>,
Gabor Gombas <gombasgg@gmail.com>,
Derrick Stolee <stolee@gmail.com>
Subject: Re: [PATCH] advice: recommend GIT_ADVICE=0 for tools
Date: Thu, 05 Sep 2024 13:26:15 -0700 [thread overview]
Message-ID: <xmqq4j6t26fs.fsf@gitster.g> (raw)
In-Reply-To: <pull.1781.git.1725559154387.gitgitgadget@gmail.com> (Derrick Stolee via GitGitGadget's message of "Thu, 05 Sep 2024 17:59:14 +0000")
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> advice.*::
> These variables control various optional help messages designed to
> - aid new users. When left unconfigured, Git will give the message
> - alongside instructions on how to squelch it. You can tell Git
> - that you do not need the help message by setting these to `false`:
> + aid new users. These are output to `stderr` by default as they are
> + intended to help human readers. Tools that execute Git as a subprocess
> + can disable these messages by setting `GIT_ACVICE=0` in the environment.
> ++
> +When left unconfigured, Git will give the message alongside instructions on how
> +to squelch it. You can tell Git that you do not need the help message by
> +setting these to `false`:
This somehow makes it sounds like it is an "aside, by the way" that
these trigger by default and that you can selectively disable it by
setting these variables, but shouldn't the stress be the other way
around? Shouldn't the mention of GIT_ADVICE be a side note, leaving
primary text target human users?
Perhaps like this?
Thanks.
Documentation/config/advice.txt | 8 +++++++-
Documentation/git.txt | 11 +++++++++++
2 files changed, 18 insertions(+), 1 deletion(-)
diff --git c/Documentation/config/advice.txt w/Documentation/config/advice.txt
index 0ba8989820..d749aee7f4 100644
--- c/Documentation/config/advice.txt
+++ w/Documentation/config/advice.txt
@@ -2,7 +2,13 @@ advice.*::
These variables control various optional help messages designed to
aid new users. When left unconfigured, Git will give the message
alongside instructions on how to squelch it. You can tell Git
- that you do not need the help message by setting these to `false`:
+ that you have understood the issue and no longer need a specific
+ help message by setting the corresponding variable to `false`.
++
+As they are intended to help human users, these messages are output
+to the standard error. When tools that run Git as a subprocesses
+find them disruptive, they can set `GIT_ADVICE=0` in the environment
+to squelch all advice messages.
+
--
addEmbeddedRepo::
diff --git c/Documentation/git.txt w/Documentation/git.txt
index 4489e2297a..d15a869762 100644
--- c/Documentation/git.txt
+++ w/Documentation/git.txt
@@ -1027,6 +1027,17 @@ standard output.
adequate and support for it is likely to be removed in the
foreseeable future (along with the variable).
+`GIT_ADVICE`::
+ If set to `0`, then disable all advice messages. These messages are
+ intended to provide hints to human users that may help them get out of
+ problematic situations or take advantage of new features. Users can
+ disable individual messages using the `advice.*` config keys. These
+ messages may be disruptive to tools that execute Git processes, so this
+ variable is available to disable the messages. (The `--no-advice`
+ global option is also available, but old Git versions may fail when
+ this option is not understood. The environment variable will be ignored
+ by Git versions that do not understand it.)
+
Discussion[[Discussion]]
------------------------
next prev parent reply other threads:[~2024-09-05 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 17:59 [PATCH] advice: recommend GIT_ADVICE=0 for tools Derrick Stolee via GitGitGadget
2024-09-05 18:02 ` Eric Sunshine
2024-09-06 19:47 ` Derrick Stolee
2024-09-05 20:26 ` Junio C Hamano [this message]
2024-09-06 19:49 ` Derrick Stolee
2024-09-06 20:22 ` [PATCH v2] " Derrick Stolee via GitGitGadget
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=xmqq4j6t26fs.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gombasgg@gmail.com \
--cc=james@jamesliu.io \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=stolee@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).