Jeff King <peff@xxxxxxxx> writes: > If you take my suggestion on patch 3, then the only other caller of > map_loose_object_1() goes away, and we can fold it all into one > reasonably-named function: Ah, that is true as of this patch, but patch 3 introduces another caller of this function. I tried to allude to it in the commit message, but if there is a clearer way to explain that, please let me know.