Re: [PATCH v2 0/4] add ref content check for files backend

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 29, 2024, 16:12 UTC
Message-ID: <xmqqmskvwbnp.fsf@gitster.g>
In-Reply-To: <ZtCYMiOXVUM7SD3v@ArchLinux>

shejialuo <shejialuo@gmail.com> writes:

Show 5 quoted lines

> From my current understanding, I think I need to rebase two patches
> provided by your here:
>
>   https://lore.kernel.org/git/xmqqle0gzdyh.fsf_-_@gitster.g/
>   https://lore.kernel.org/git/xmqqbk1cz69c.fsf@gitster.g/

They are to be squashed into your patch, "suggested edit" for your changes, not "to be rebased". In other words, we do not want to see a patch (from your v2 as-is) to create problems and then another patch (taken from one of these links) applied on top to remedy them. We instead want to see a patch (start from your v2 but with the changes from these links) that does not introduce problems in the first place.

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