• Junio C Hamano's avatar
    inline lookup_replace_object() calls · e1111cef
    Junio C Hamano authored
    In a repository without object replacement, lookup_replace_object() should
    be a no-op. Check the flag "read_replace_refs" on the side of the caller,
    and bypess a function call when we know we are not dealing with replacement.
    
    Also, even when we are set up to replace objects, if we do not find any
    replacement defined, flip that flag off to avoid function call overhead
    for all the later object accesses.
    
    As this change the semantics of the flag from "do we need read the
    replacement definition?" to "do we need to check with the lookup table?"
    the flag needs to be renamed later to something saner, e.g. "use_replace",
    when the codebase is calmer, but not now.
    Signed-off-by: default avatarJunio C Hamano <[email protected]>
    e1111cef
replace_object.c 2.66 KB