From: Junio C Hamano <gitster@pobox.com>
To: "Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Han-Wen Nienhuys <hanwenn@gmail.com>,
Han-Wen Nienhuys <hanwen@google.com>
Subject: Re: [PATCH 2/2] refs: set the repo in debug_ref_store.base
Date: Tue, 21 Dec 2021 21:58:44 -0800 [thread overview]
Message-ID: <xmqqtuf1kwob.fsf@gitster.g> (raw)
In-Reply-To: <75e5392032dbdbdedf8a2b76a7098e4dc1133d82.1640090038.git.gitgitgadget@gmail.com> (Han-Wen Nienhuys via GitGitGadget's message of "Tue, 21 Dec 2021 12:33:58 +0000")
"Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Han-Wen Nienhuys <hanwen@google.com>
>
> This is for consistency with the files backend.
Hmmmm. Could you explain what it exactly means?
I can see that files_ref_store structure has the .repo member and
files_ref_store_create() uses it to remember which repository the
ref store is for, but that is an implementation detail that is not
exposed outside the files backend, isn't it?
To put it differently, what is broken with the current code that
leaves the .repo member in refs->base uninitialized? We are
presumably helping the caller that wants to know the repository the
ref store belongs to via this pointer with this change---what is
that caller?
> Signed-off-by: Han-Wen Nienhuys <hanwen@google.com>
> ---
> refs/debug.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/refs/debug.c b/refs/debug.c
> index cf6ad36fbb0..136cfd7c700 100644
> --- a/refs/debug.c
> +++ b/refs/debug.c
> @@ -26,6 +26,7 @@ struct ref_store *maybe_debug_wrap_ref_store(const char *gitdir, struct ref_stor
> be_copy->name = store->be->name;
> trace_printf_key(&trace_refs, "ref_store for %s\n", gitdir);
> res->refs = store;
> + res->base.repo = store->repo;
> base_ref_store_init((struct ref_store *)res, be_copy);
> return (struct ref_store *)res;
> }
Thanks.
next prev parent reply other threads:[~2021-12-22 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 12:33 [PATCH 0/2] tweaks to refs/debug.c Han-Wen Nienhuys via GitGitGadget
2021-12-21 12:33 ` [PATCH 1/2] refs: print error message in debug output Han-Wen Nienhuys via GitGitGadget
2021-12-21 12:33 ` [PATCH 2/2] refs: set the repo in debug_ref_store.base Han-Wen Nienhuys via GitGitGadget
2021-12-22 5:58 ` Junio C Hamano [this message]
2021-12-22 18:13 ` Han-Wen Nienhuys
2021-12-22 18:11 ` [PATCH v2 0/3] tweaks to refs/debug.c Han-Wen Nienhuys via GitGitGadget
2021-12-22 18:11 ` [PATCH v2 1/3] refs: pass gitdir to packed_ref_store_create Han-Wen Nienhuys via GitGitGadget
2021-12-22 18:11 ` [PATCH v2 2/3] refs: print error message in debug output Han-Wen Nienhuys via GitGitGadget
2021-12-22 18:11 ` [PATCH v2 3/3] refs: centralize initialization of the base ref_store Han-Wen Nienhuys via GitGitGadget
2021-12-22 21:54 ` [PATCH v2 0/3] tweaks to refs/debug.c Junio C Hamano
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=xmqqtuf1kwob.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hanwen@google.com \
--cc=hanwenn@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).