From: Junio C Hamano <gitster@pobox.com>
To: Tian Yuchen <cat@malon.dev>
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: Thu, 12 Mar 2026 12:58:43 -0700 [thread overview]
Message-ID: <xmqqfr64es5o.fsf@gitster.g> (raw)
In-Reply-To: <2c9861c0-fdac-4123-8cd9-4a841755abf3@malon.dev> (Tian Yuchen's message of "Fri, 13 Mar 2026 02:49:05 +0800")
Tian Yuchen <cat@malon.dev> writes:
>> 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.
Nah, I think we do want to keep it; once it is written, it is a
waste to discard it, especially given that the change is not wrong
per-se. If anything else, having it will save somebody else time
and effort to do the same thing again ;-).
Thanks.
prev parent reply other threads:[~2026-03-12 19:58 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
2026-03-12 19:58 ` Junio C Hamano [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=xmqqfr64es5o.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=cat@malon.dev \
--cc=git@vger.kernel.org \
--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 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.