Re: [PATCH v3 2/4] object-file: refactor map_loose_object_1()
- From
- Jonathan Tan <jonathantanmy@google.com>
- Date
- Dec 9, 2022, 18:17 UTC
- Message-ID
- <20221209181704.106534-1-jonathantanmy@google.com>
- In-Reply-To
- <Y5KWpXwxdRI4QPNl@coredump.intra.peff.net>
Jeff King <peff@peff.net> 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.