Subject: Re: [PATCH v3 00/14] ref-transactions-reflog

From: Junio C Hamano <[email-masked]>
Date: Thu, 20 Nov 2014 09:34:01 -0800

Jonathan Nieder <[email-masked]> writes:

> I also have some thoughts about how those operations can be
> implemented without such a performance hit (reading the whole
> reflog into memory as part of the transaction seems problematic to
> me), but that should probably wait for a separate message (and
> I've talked about it a bit in person).

Perhaps iterator interface such as for_each_reflog_ent() would help?