Thread (2 messages) flat view 2 messages, 2 authors, 2021-08-19

Re: [PATCH v2 09/11] reflog expire: don't lock reflogs using previously seen OID

From: Junio C Hamano <hidden>
Date: 2021-08-18 21:05:19

Possibly related (same subject, not in this thread)

Han-Wen Nienhuys [off-list ref] writes:
On Fri, Jul 16, 2021 at 4:13 PM Ævar Arnfjörð Bjarmason
[off-list ref] wrote:
quoted
-                       status |= reflog_expire(e->reflog, &e->oid, flags,
+                       status |= reflog_expire(e->reflog, NULL, flags,
                                                reflog_expiry_prepare,
this causes reflog_expiry_prepare() to be called with a NULL oid. I'm
seeing a crash in do_lookup_replace_object() because of this in
t0031-reftable.sh.
Yeah, given that reflog_expire() is documented to take "oid is the
old value of the reference", the change looks bogus to me too.

Ævar, what is going on here?

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help