Re: [PATCH 1/3] doc: clarify documentation for rename/copy limits

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 12, 2021, 21:27 UTC
Message-ID: <xmqqh7gz2pfe.fsf@gitster.g>
In-Reply-To: <c25e29a9-3a15-4079-43fd-b77746927b16@gmail.com>

Derrick Stolee <stolee@gmail.com> writes:

Show 8 quoted lines

>   merge.renameLimit::
>       The number of potential inexact renames to consider when
>       performing rename detection during a merge; if this limit
>       is exceeded, then no inexact renames are computed. Renames
>       where the content does not change are excluded from this
>       limit. If not specified, defaults to...
>
> Feel free to take or leave any of this example.

Phrases like "finding inexact renames" and "finding which files were moved with changes" may tell what we are spending cycles on to the end user, but I have to say I agree that "quadratic portion" would not resonate with the intended audiences at all.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.