Re: Proposal: tell git a file has been renamed

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 26, 2023, 20:39 UTC
Message-ID: <xmqqwn1yqsx7.fsf@gitster.g>
In-Reply-To: <c7bb292d-903b-692e-885b-524b6bb113ee@intel.com>

Jacob Keller <jacob.e.keller@intel.com> writes:

Show 6 quoted lines

> The alternative would be something like Junio suggested where we have a
> separate rename storage database which is computed ahead of time (kind
> of like commit graph storage) and which could be overridden manually.
> This doesn't "bake" anything into the objects, but obviously requires
> manually keeping up to date and adds some difficulty in sharing such
> updates across remotes.

I think originally the recorded rename mechanism was dreamed up to be a cache. Unlike commit-graph that requires precomputation, it would be populated incrementally when you run "git log -M" in a part of the history that you haven't done so. Sharing it would just be as hard as sharing notes, once we point the rename cache with a ref, I would think.

I cannot take credit for the idea, though.