From: Phillip Wood <phillip.wood123@gmail.com>
To: Andrew Pleeter via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Andrew Pleeter <andrewpleeter@gmail.com>
Subject: Re: [PATCH v3] var: support broken-down idents, default key, multiple args, and -z
Date: Fri, 4 Sep 2026 10:11:30 +0100 [thread overview]
Message-ID: <5634fdc4-d0f8-493d-b401-3c9753524034@gmail.com> (raw)
In-Reply-To: <pull.2388.v3.git.git.1788403792962.gitgitgadget@gmail.com>
Hi Andrew
On 03/09/2026 03:49, Andrew Pleeter via GitGitGadget wrote:
> From: Andrew Pleeter <andrewpleeter@gmail.com>
>
> - Support '-z' to terminate variable outputs and 'git var -l -z'
> entries with NUL bytes.
Hurray! I agree with Junios comments and have left a few of my own below.
> static const struct git_var *get_git_var(const char *var)
> {
> struct git_var *ptr;
> + if (!strcmp(var, "GIT_SIGNING_KEY"))
> + var = "GIT_DEFAULT_KEY";
Do we really need an alias? GIT_DEFAULT_KEY is pretty meaningless to me,
whereas GIT_SIGNING_KEY is clearly a key for signing. What's the usecase
for this by the way. If a script is using git to sign then it does not
need to query the default key because git will use it automatically. If
a script wants to use the key to sign something else doesn't it need to
also know which signing scheme git is using (ssh, gpg, etc) , or is that
obvious from the key?
> for (ptr = git_vars; ptr->read; ptr++) {
> if (strcmp(var, ptr->name) == 0) {
> return ptr;
> @@ -207,10 +316,13 @@ static const struct git_var *get_git_var(const char *var)
> static int show_config(const char *var, const char *value,
> const struct config_context *ctx, void *cb)
> {
> + int null_term = cb ? *(int *)cb : 0;
> + char eol = null_term ? '\0' : '\n';
> +
> if (value)
> - printf("%s=%s\n", var, value);
> + printf("%s=%s%c", var, value, eol);
A key can contain "=" so this format is ambiguous. When the user passes
"-z" we should use the same format as "git config list -z" which avoids
that ambiguity
printf("%s%c%s%c", var, eol == '\n' ? '=' : '\n', value, eol);
> else
> - printf("%s\n", var);
> + printf("%s%c", var, eol);
It would be worth checking what "git config list -z" does when there is
no value and matching that. Does it print "key\n\0", or "key\0"?
> + for (i = 1; i < argc; i++) {
> + const char *arg = argv[i];
> +
> + if (!strcmp(arg, "-l")) {
> + list = 1;
> + } else if (!strcmp(arg, "-z")) {
> + null_term = 1;
> + } else if (!strcmp(arg, "--")) {
> + for (i = i + 1; i < argc; i++)
> + strvec_push(&vars, argv[i]);
> + break;
> + } else if (arg[0] == '-') {
> + usage(var_usage);
> + } else {
> + strvec_push(&vars, arg);
I think we should break out of the loop when arg is "--", or does not
begin with '-', and treat the rest as variable names to print. There is
not need to support "git var GIT_AUTHOR_NAME -z GIT_AUTHOR_EMAIL" in a
plumbing command.
> [...]
> - printf("%s\n", val);
> - free(val);
> + printf("%s%c", val, null_term ? '\0' : '\n');
Multi-valued variables are a bit of a problem here, they're built on the
assumption that the individual values do not contain a newline, but as
they are paths I'm not sure that is necessarily true. With -z it would
be better to print '\0' after each value as we do in list_vars().
Ideally we wouldn't use a single string to pass multiple values around,
but a simple fix would be to use '\0' to separate the individual values
instead of '\n' so that we can split them unambiguously when we print them.
Thanks for working on this, being able to specify multiple variables
that are printed unambiguously is a really useful improvement.
Phillip
> + free(val);
> + }
>
> + strvec_clear(&vars);
> return 0;
> }
> diff --git a/t/t0007-git-var.sh b/t/t0007-git-var.sh
> index 2b60317758..c437c968bb 100755
> --- a/t/t0007-git-var.sh
> +++ b/t/t0007-git-var.sh
> @@ -276,4 +276,81 @@ test_expect_success '`git var -l` works even without HOME' '
> )
> '
>
> +test_expect_success 'get author identity components' '
> + test_tick &&
> + echo "$GIT_AUTHOR_NAME" >expect.name &&
> + echo "$GIT_AUTHOR_EMAIL" >expect.email &&
> + echo "$GIT_AUTHOR_DATE" >expect.date &&
> + git var GIT_AUTHOR_NAME >actual.name &&
> + git var GIT_AUTHOR_EMAIL >actual.email &&
> + git var GIT_AUTHOR_DATE >actual.date &&
> + test_cmp expect.name actual.name &&
> + test_cmp expect.email actual.email &&
> + test_cmp expect.date actual.date
> +'
> +
> +test_expect_success 'get committer identity components' '
> + test_tick &&
> + echo "$GIT_COMMITTER_NAME" >expect.name &&
> + echo "$GIT_COMMITTER_EMAIL" >expect.email &&
> + echo "$GIT_COMMITTER_DATE" >expect.date &&
> + git var GIT_COMMITTER_NAME >actual.name &&
> + git var GIT_COMMITTER_EMAIL >actual.email &&
> + git var GIT_COMMITTER_DATE >actual.date &&
> + test_cmp expect.name actual.name &&
> + test_cmp expect.email actual.email &&
> + test_cmp expect.date actual.date
> +'
> +
> +test_expect_success 'get multiple variables' '
> + test_tick &&
> + cat >expect <<-EOF &&
> + $GIT_AUTHOR_NAME
> + $GIT_AUTHOR_EMAIL
> + $GIT_COMMITTER_NAME
> + $GIT_COMMITTER_EMAIL
> + EOF
> + git var GIT_AUTHOR_NAME GIT_AUTHOR_EMAIL GIT_COMMITTER_NAME GIT_COMMITTER_EMAIL >actual &&
> + test_cmp expect actual
> +'
> +
> +test_expect_success 'get multiple variables with -z' '
> + test_tick &&
> + printf "%s\0%s\0" "$GIT_AUTHOR_NAME" "$GIT_AUTHOR_EMAIL" >expect &&
> + git var -z GIT_AUTHOR_NAME GIT_AUTHOR_EMAIL >actual &&
> + test_cmp expect actual
> +'
> +
> +test_expect_success 'git var -l -z' '
> + git var -l -z >actual &&
> + tr "\0" "\n" <actual | grep "^GIT_AUTHOR_NAME=" >filtered &&
> + echo "GIT_AUTHOR_NAME=$GIT_AUTHOR_NAME" >expect &&
> + test_cmp expect filtered
> +'
> +
> +test_expect_success 'get GIT_DEFAULT_KEY with user.signingkey configured' '
> + test_config user.signingkey "TEST_KEY_ID" &&
> + echo "TEST_KEY_ID" >expect &&
> + git var GIT_DEFAULT_KEY >actual &&
> + test_cmp expect actual &&
> + git var GIT_SIGNING_KEY >actual.alias &&
> + test_cmp expect actual.alias
> +'
> +
> +test_expect_success 'get GIT_DEFAULT_KEY fails when unset and signing disabled' '
> + test_config user.signingkey "" &&
> + test_config commit.gpgsign false &&
> + test_must_fail git var GIT_DEFAULT_KEY
> +'
> +
> +test_expect_success 'git var -l lists new variables' '
> + git var -l >actual &&
> + grep "^GIT_AUTHOR_NAME=" actual &&
> + grep "^GIT_AUTHOR_EMAIL=" actual &&
> + grep "^GIT_AUTHOR_DATE=" actual &&
> + grep "^GIT_COMMITTER_NAME=" actual &&
> + grep "^GIT_COMMITTER_EMAIL=" actual &&
> + grep "^GIT_COMMITTER_DATE=" actual
> +'
> +
> test_done
>
> base-commit: 2c3adbb2c475981e340c79fdc5e7f4f9b5d9054e
next prev parent reply other threads:[~2026-09-04 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 20:46 [PATCH] builtin/whoami: add new 'whoami' command Andrew Pleeter via GitGitGadget
2026-08-25 21:24 ` brian m. carlson
2026-08-25 21:41 ` Junio C Hamano
2026-08-31 23:59 ` [PATCH v2] builtin/ident: add new 'ident' command Andrew Pleeter via GitGitGadget
2026-09-01 4:39 ` Jeff King
2026-09-01 5:00 ` Junio C Hamano
2026-09-03 2:49 ` [PATCH v3] var: support broken-down idents, default key, multiple args, and -z Andrew Pleeter via GitGitGadget
2026-09-03 17:40 ` Junio C Hamano
2026-09-03 18:22 ` Ben Knoble
2026-09-04 9:11 ` Phillip Wood [this message]
2026-09-04 15:57 ` Junio C Hamano
2026-09-08 9:07 ` Phillip Wood
2026-09-08 4:09 ` [PATCH v4] var: support broken-down idents, signing " Andrew Pleeter via GitGitGadget
2026-09-08 13:54 ` Phillip Wood
2026-09-08 20:43 ` [PATCH v5] " Andrew Pleeter via GitGitGadget
2026-09-08 21:53 ` Junio C Hamano
2026-09-09 1:24 ` [PATCH v6] " Andrew Pleeter via GitGitGadget
2026-09-09 15:36 ` Phillip Wood
2026-09-09 16:42 ` Junio C Hamano
2026-09-10 3:09 ` [PATCH v7] " Andrew Pleeter 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=5634fdc4-d0f8-493d-b401-3c9753524034@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=andrewpleeter@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=phillip.wood@dunelm.org.uk \
--cc=sandals@crustytoothpaste.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.