Re: [PATCH v2 24/24] Rename functions to avoid breaking in-flight topics

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 11, 2018, 16:58 UTC
Message-ID: <xmqq1sa0q8d8.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CACsJy8CepuW3DG2AbMiHdoUELHfBmMSZDtPJMzLRHUWwshvivw@mail.gmail.com>

Duy Nguyen <pclouds@gmail.com> writes:

Show 5 quoted lines

> In the end, there's no variant, only one function that always takes
> 'struct repository *' and I wanted to keep the shorter name 'rerere'.
> But let's go with adding repo_rerere() and deprecating rerere(). If it
> turns out later that repo_rerere is too long (or it's repo_xyz
> everywhere) then we can do another rename.

Yup, I am not opposed to another rename after the dust settles, but do nto want to see it as part of the series.

Thanks.

$ 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.