Re: Determining whether you have a commit locally, in a partial clone?

[Tao Klerks <tao@klerks.biz>]

On Tue, Jun 20, 2023 at 2:04 PM Tao Klerks <tao@klerks.biz> wrote:
>
> On Tue, Jun 20, 2023 at 1:26 PM Tao Klerks <tao@klerks.biz> wrote:
> >
> > * Is there any way to run a single git command in a "don't use
> > promisors" context?
>
> My apologies for the self-reply, I did find a workaround here:
>
> git -c remote.origin.url log SOME_HASH_NOT_IN_REFSPEC
>

Another self-reply unfortunately: This workaround stops working in git 2.39 :(

I haven't understood exactly what's going on, but I guess the fetch
failure was explicitly curtailing *something* extremely expensive that
gets to go forward anyway as of 2.39.

I imagine it's related to the changelog entry "Remove error detection
from a function that fetches from promisor remotes":
https://github.com/gitgitgadget/git/blob/79bdd48716a4c455bdc8ffd91d57a18d5cd55baa/Documentation/RelNotes/2.39.0.txt

I'm back to begging for any hints here: Any idea how I can determine
whether a given commit object exists locally, *without causing it to
be fetched by the act of checking for it?*

Thanks,
Tao