From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
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>
Subject: Re: [PATCH] advice: recommend GIT_ADVICE=0 for tools
Date: Fri, 6 Sep 2024 15:49:15 -0400 [thread overview]
Message-ID: <da98da07-b2f4-4608-9038-7ce4b8e2d74b@gmail.com> (raw)
In-Reply-To: <xmqq4j6t26fs.fsf@gitster.g>
On 9/5/24 4:26 PM, Junio C Hamano wrote:
> 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.
I like this a lot better. Your careful edit is substantial enough
that I will give you co-authored-by in v2.
Thanks,
-Stolee
next prev parent reply other threads:[~2024-09-06 19:49 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
2024-09-06 19:49 ` Derrick Stolee [this message]
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=da98da07-b2f4-4608-9038-7ce4b8e2d74b@gmail.com \
--to=stolee@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=gombasgg@gmail.com \
--cc=james@jamesliu.io \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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).