From: karthik nayak <karthik.188@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org, ps@pks.im, shejialuo@gmail.com,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] builtin: pass repository to sub commands
Date: Tue, 26 Nov 2024 04:50:10 -0500 [thread overview]
Message-ID: <CAOLa=ZSF6PC0dXGE8JUeeZqQgxgGAMnKJNGNeEMTwhCwN-OXYQ@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD0=OycMAaDi_92-Go2Mt4q-s7cfmBaZD_kWBnZsvYpiPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Christian Couder <christian.couder@gmail.com> writes:
> On Mon, Nov 25, 2024 at 3:56 PM Karthik Nayak <karthik.188@gmail.com> wrote:
>>
>> In 9b1cb5070f (builtin: add a repository parameter for builtin
>> functions, 2024-09-13) the repository was passed down to all builtin
>> commands. This allowed the repository to be passed down to lower layers
>> without depending on the global `the_repository` variable.
>>
>> Continue this work by also passing down the repository parameter from
>> the command to sub-commands. This will help pass down the repository to
>> other subsystems and cleanup usage of global variables like
>> 'the_repository' and 'the_hash_algo'.
>>
>> Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
>
> Yeah, this is definitely needed to cleanup usage of global variables,
> and looks well done to me. Ack.
>
Thanks for the review.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]
next prev parent reply other threads:[~2024-11-26 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 14:55 [PATCH] builtin: pass repository to sub commands Karthik Nayak
2024-11-26 8:46 ` Christian Couder
2024-11-26 9:50 ` karthik nayak [this message]
2024-11-26 8:56 ` Patrick Steinhardt
2024-11-26 9:56 ` karthik nayak
2024-11-26 19:26 ` Junio C Hamano
2024-11-26 11:19 ` [PATCH v2] builtin: allow passing custom data to sub-commands Karthik Nayak
2024-11-26 11:57 ` shejialuo
2024-11-26 16:41 ` karthik nayak
2024-11-26 19:27 ` Junio C Hamano
2024-11-27 9:15 ` karthik nayak
2024-11-27 12:23 ` karthik nayak
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='CAOLa=ZSF6PC0dXGE8JUeeZqQgxgGAMnKJNGNeEMTwhCwN-OXYQ@mail.gmail.com' \
--to=karthik.188@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
--cc=shejialuo@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).