Jonathan Nieder <jrnieder@xxxxxxxxx> 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? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html