From: Justin Tobler <jltobler@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] builtin/repo: rename "references.format" to "references.storageFormat"
Date: Tue, 13 Oct 2026 17:50:43 -0500 [thread overview]
Message-ID: <as61Dh7ui54gdzGV@denethor> (raw)
In-Reply-To: <20261005-pks-repo-ref-storage-format-v1-1-819a181572a9@pks.im>
On 26/10/05 12:14PM, Patrick Steinhardt wrote:
> As part of 2f28db44d5 (Merge branch 'ps/ref-storage-format', 2026-10-01)
> we have adapt all sites that used to say "reference format" to instead
> say "reference storage format".
>
> One missed spot though was in git-repo(1), where we still print the
> "references.format" key. Fix that oversight by renaming the key to
> "references.storageFormat".
Being that git-repo(1) is a recent command and still marked as
experimental, I think making this change to be consistent is completely
reasonable. It makes sense to keep the naming unified.
>
> Signed-off-by: Patrick Steinhardt <ps@pks.im>
> ---
> Hi,
>
> this is a follow-up on 2f28db44d5 (Merge branch 'ps/ref-storage-format',
> 2026-10-01), where I missed this one place. I noticed that only today
> while working on the object storage format extension.
>
> Thanks!
>
> Patrick
> ---
> Documentation/git-repo.adoc | 6 +++---
> builtin/repo.c | 2 +-
> t/t1900-repo-info.sh | 12 ++++++------
> 3 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/git-repo.adoc b/Documentation/git-repo.adoc
> index ed7d80c690..5af454e8ca 100644
> --- a/Documentation/git-repo.adoc
> +++ b/Documentation/git-repo.adoc
> @@ -119,7 +119,7 @@ values that they return:
> `path.gitdir.relative`::
> The path to the Git repository directory relative to the current working directory.
>
> -`references.format`::
> +`references.storageFormat`::
> The reference storage format. The valid values are:
> +
> include::ref-storage-format.adoc[]
> @@ -127,10 +127,10 @@ include::ref-storage-format.adoc[]
> EXAMPLES
> --------
>
> -* Retrieves the reference format of the current repository:
> +* Retrieves the reference storage format of the current repository:
> +
> ------------
> -git repo info references.format
> +git repo info references.storageFormat
> ------------
> +
>
> diff --git a/builtin/repo.c b/builtin/repo.c
> index 84e012f83f..15267e8d54 100644
> --- a/builtin/repo.c
> +++ b/builtin/repo.c
> @@ -137,7 +137,7 @@ static const struct repo_info_field repo_info_field[] = {
> { "path.commondir.relative", get_path_commondir_relative },
> { "path.gitdir.absolute", get_path_gitdir_absolute },
> { "path.gitdir.relative", get_path_gitdir_relative },
> - { "references.format", get_references_format },
> + { "references.storageFormat", get_references_format },
Here we change the key name. The rest of this patch looks trivially
correct.
-Justin
prev parent reply other threads:[~2026-10-13 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:14 [PATCH] builtin/repo: rename "references.format" to "references.storageFormat" Patrick Steinhardt
2026-10-05 15:11 ` Karthik Nayak
2026-10-06 5:53 ` Patrick Steinhardt
2026-10-06 11:57 ` Karthik Nayak
2026-10-13 22:50 ` Justin Tobler [this message]
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=as61Dh7ui54gdzGV@denethor \
--to=jltobler@gmail.com \
--cc=git@vger.kernel.org \
--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 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.