From: Patrick Steinhardt <ps@pks.im>
To: Justin Tobler <jltobler@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/6] builtin/receive-pack: pass shallow file explicitly
Date: Fri, 7 Aug 2026 09:03:33 +0200 [thread overview]
Message-ID: <anWDRVA0mSQva2QX@pks.im> (raw)
In-Reply-To: <20260806213859.816157-3-jltobler@gmail.com>
On Thu, Aug 06, 2026 at 04:38:55PM -0500, Justin Tobler wrote:
> diff --git a/builtin/receive-pack.c b/builtin/receive-pack.c
> index 420de9aa7f..6da854fca2 100644
> --- a/builtin/receive-pack.c
> +++ b/builtin/receive-pack.c
> @@ -86,7 +86,6 @@ static const char *head_name;
> static void *head_name_to_free;
> static int sent_capabilities;
> static int shallow_update;
> -static const char *alt_shallow_file;
> static struct strbuf push_cert = STRBUF_INIT;
> static struct object_id push_cert_oid;
> static struct signature_check sigcheck;
I always like seeing less global state.
> @@ -2354,10 +2353,9 @@ static const char *unpack(int err_fd, struct shallow_info *si,
> return hdr_err;
> }
>
> - if (si->nr_ours || si->nr_theirs) {
> - alt_shallow_file = setup_temporary_shallow(si->shallow);
> + if (shallow_file) {
> strvec_push(&child.args, "--shallow-file");
> - strvec_push(&child.args, alt_shallow_file);
> + strvec_push(&child.args, shallow_file);
> }
>
> odb_transaction_env(transaction, &child.env);
Okay, so instead of creating the shallow file here, ...
> @@ -2705,11 +2705,17 @@ int cmd_receive_pack(int argc,
> if (!si.nr_ours && !si.nr_theirs)
> shallow_update = 0;
> if (!delete_only(commands)) {
> + const char *alt_shallow_file = NULL;
> +
> + if (si.nr_ours || si.nr_theirs)
> + alt_shallow_file = setup_temporary_shallow(si.shallow);
> +
> if (odb_transaction_begin(the_repository->objects, &transaction, ODB_TRANSACTION_RECEIVE))
> unpack_status = "unable to start object transaction";
> else
> - unpack_status = unpack_with_sideband(&si, transaction);
> - update_shallow_info(commands, &si, &ref);
> + unpack_status = unpack_with_sideband(transaction, alt_shallow_file);
> +
> + update_shallow_info(commands, &si, &ref, alt_shallow_file);
> }
... we create it in a transitive caller and then pass it down the stack.
Makes sense.
It's nice that we don't have to pass the shallow information at all
anymore as a consequence.
Patrick
next prev parent reply other threads:[~2026-08-07 7:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 21:38 [PATCH 0/6] builtin/receive-pack: support pluggable packfile writes Justin Tobler
2026-08-06 21:38 ` [PATCH 1/6] odb/transaction: add transaction release interface Justin Tobler
2026-08-07 7:03 ` Patrick Steinhardt
2026-08-07 15:11 ` Justin Tobler
2026-08-06 21:38 ` [PATCH 2/6] builtin/receive-pack: pass shallow file explicitly Justin Tobler
2026-08-07 7:03 ` Patrick Steinhardt [this message]
2026-08-06 21:38 ` [PATCH 3/6] builtin/receive-pack: lift global state out of unpack() Justin Tobler
2026-08-07 7:03 ` Patrick Steinhardt
2026-08-07 15:33 ` Justin Tobler
2026-08-06 21:38 ` [PATCH 4/6] builtin/receive-pack: report unpack errors via strbuf Justin Tobler
2026-08-07 7:03 ` Patrick Steinhardt
2026-08-07 15:36 ` Justin Tobler
2026-08-06 21:38 ` [PATCH 5/6] builtin/receive-pack: explicitly pass packfile fd Justin Tobler
2026-08-06 21:38 ` [PATCH 6/6] odb/transaction: add transaction interface to write packfiles Justin Tobler
2026-08-07 7:03 ` Patrick Steinhardt
2026-08-07 16:01 ` Justin Tobler
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=anWDRVA0mSQva2QX@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=jltobler@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