From: Ben Knoble <ben.knoble@gmail.com>
To: Vsevolod Myalitsin <ub4nal@mail.ru>
Cc: git@vger.kernel.org, Vsevolod Myalitsin <ub4nal@mail.ru>
Subject: Re: [PATCH] advice: use global config for default branch name
Date: Tue, 8 Sep 2026 09:35:04 -0400 [thread overview]
Message-ID: <90671DEB-7A41-47DA-B865-AB963AEC11D1@gmail.com> (raw)
In-Reply-To: <20260907125610.23458-1-ub4nal@mail.ru>
> Le 7 sept. 2026 à 09:02, Vsevolod Myalitsin <ub4nal@mail.ru> a écrit :
>
> The advice for configuring the default branch name
> suggests disabling it with "git config set
> advice.defaultBranchName false". This setting is
> useless because it neither affects the current
> repository nor newly created repositories.
Makes sense.
> Suggest using "git config --global" instead.
I think we should probably say “git config set --global …”
using the modern forms, no?
> Signed-off-by: Vsevolod Myalitsin <ub4nal@mail.ru>
> ---
> advice.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/advice.c b/advice.c
> index 63bf8b0c5f..64ca4613b4 100644
> --- a/advice.c
> +++ b/advice.c
> @@ -96,7 +96,7 @@ static struct {
>
> static const char turn_off_instructions[] =
> N_("\n"
> - "Disable this message with \"git config set advice.%s false\"");
> + "Disable this message with \"git config %s advice.%s false\"");
>
> static void vadvise(const char *advice, int display_instructions,
> const char *key, va_list params)
> @@ -107,7 +107,8 @@ static void vadvise(const char *advice, int display_instructions,
> strbuf_vaddf(&buf, advice, params);
>
> if (display_instructions)
> - strbuf_addf(&buf, turn_off_instructions, key);
> + strbuf_addf(&buf, turn_off_instructions,
> + strcmp(key, "defaultBranchName") ? "set" : "--global", key);
This would be hard to extend later for other advice options that also make more sense at the global level. Perhaps extract a little helper is_global(key)?
Thanks
next prev parent reply other threads:[~2026-09-08 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 12:56 [PATCH] advice: use global config for default branch name Vsevolod Myalitsin
2026-09-08 13:35 ` Ben Knoble [this message]
2026-09-08 18:56 ` Vsevolod Myalitsin
2026-09-08 14:59 ` Ben Knoble
2026-09-08 19:56 ` R4NC
2026-09-08 16:24 ` D. Ben Knoble
2026-09-08 16:31 ` Junio C Hamano
2026-09-08 21:38 ` Vsevolod Myalitsin
2026-09-08 18:57 ` Junio C Hamano
2026-09-09 6:49 ` R4NC
2026-09-09 15:54 ` Jeff King
2026-09-09 18:51 ` Junio C Hamano
2026-09-09 19:51 ` Jeff King
2026-09-10 4:23 ` Junio C Hamano
2026-09-10 4:33 ` Jeff King
2026-09-10 12:18 ` Junio C Hamano
2026-09-10 16:31 ` Jeff King
2026-09-10 4:28 ` Junio C Hamano
2027-08-29 0:59 ` Vsevolod Myalitsin
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=90671DEB-7A41-47DA-B865-AB963AEC11D1@gmail.com \
--to=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=ub4nal@mail.ru \
/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