From: Tian Yuchen <cat@malon.dev>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, karthik.188@gmail.com,
phillip.wood@dunelm.org.uk, jltobler@gmail.com, ps@pks.im
Subject: Re: [PATCH v2] builtin/mktree: remove USE_THE_REPOSITORY_VARIABLE
Date: Fri, 13 Mar 2026 02:49:05 +0800 [thread overview]
Message-ID: <2c9861c0-fdac-4123-8cd9-4a841755abf3@malon.dev> (raw)
In-Reply-To: <xmqqsea5ezwl.fsf@gitster.g>
Hi Junio,
> RUN_SETUP also guarantees that the repo points at the_repository.
>
> The patch is not wrong per-se, but at the same time, it is not a
> very interesting change exactly for this reason.
>
> Where did you read that dropping USE_THE_REPOSITORY_VARIABLE is a
> good idea?
I mentioned this at the bottom of v1:
> I originally intended to attempt the #FIXME in t1006-cat-file.sh.
> I followed the clues all the way here, only to discover that the
> FIXME required a level of expertise far beyond my capabilities,
> so I gave up. However, I spot the global variable here, so I went
> ahead and fixed it 😉
In other words, I just happened to see this thing. I didn't go looking
for it ;)
> As somebody (Phillip?) said earlier, we probably should update
> document and clearly say that removing USE_THE_REPOSITORY_VARIABLE
> is not a high-value target when done in the builtin/ directory, even
> though it is very desirable thing to do for more library-ish part of
> the codebase.
I am fully aware of this, and I did not specifically modify
the_repository in builtin/ during previous patches. It's just that this
macro makes me particularly uncomfortable, and I believe it would be
better to remove it.
On the other hand, this patch is indeed boring and useless. Feel free to
ignore it.
Regards,
Yuchen
next prev parent reply other threads:[~2026-03-12 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 16:42 [PATCH v2] builtin/mktree: remove USE_THE_REPOSITORY_VARIABLE Tian Yuchen
2026-03-12 17:11 ` Junio C Hamano
2026-03-12 18:49 ` Tian Yuchen [this message]
2026-03-12 19:58 ` 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=2c9861c0-fdac-4123-8cd9-4a841755abf3@malon.dev \
--to=cat@malon.dev \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jltobler@gmail.com \
--cc=karthik.188@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox