From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] read-cache: hide refresh_cache_entry()
Date: Mon, 02 Nov 2026 11:00:57 -0800 [thread overview]
Message-ID: <xmqqld7bhxcm.fsf@gitster.g> (raw)
In-Reply-To: <auhbjFvD8CNXYcgQ@pks.im> (Patrick Steinhardt's message of "Mon, 2 Nov 2026 10:44:44 +0100")
Patrick Steinhardt <ps@pks.im> writes:
>> > Could we avoid this forward declaration by moving the function around?
>>
>> As refresh_cache_entry() that has mere one line in its body calls
>> refresh_cache_ent() that is a screenful and defined nearby, both of
>> them need to be moved upward, so it becomes a rather unsightly
>> change, even though nobody would care when they only look at the end
>> result X-<.
>
> Well, people probably know by now that I myself tend to err more on the
> side of fixing up stuff, even if it's a bit more on the painful side of
> things. So I'm not going to surprise you by saying that I think that
> would be worth it.
>
> In any case, I don't feel strongly about it.
FWIW, the version with large code movement will be the final
version, as my philosophy is "once written, unless there is a
compelling reason, do not flip flop" and the last one I wrote was
the one you suggested, so that I can see how bad the result looks.
I think the patch itself may be ugly but the result is easier to
work on going forward. Thanks for pushing.
prev parent reply other threads:[~2026-11-02 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 20:34 [PATCH] read-cache: hide refresh_cache_entry() Junio C Hamano
2026-10-30 9:43 ` Patrick Steinhardt
2026-10-30 15:46 ` Junio C Hamano
2026-11-02 9:44 ` Patrick Steinhardt
2026-11-02 19:00 ` 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=xmqqld7bhxcm.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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