Re: [PATCH v5 0/9] add ref content check for files backend

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 30, 2024, 18:57 UTC
Message-ID: <xmqqikud6kc0.fsf@gitster.g>
In-Reply-To: <Zvj-DgHqtC30KjJe@ArchLinux>

shejialuo <shejialuo@gmail.com> writes:

> Because I do not sync the upstream for a long time. For this series, I
> sync the latest upstream and generate the patch, it is based on
>
>   3857aae53f (Git 2.47-rc0, 2024-09-25)

Does this help to reduce conflicts when merging the topic to say 'next' or 'seen'? If so, such a rebase and noting it in the cover letter message, like you just did, is very much appreciated.

If not, please don't ;-).

> And I don't think range-diff is useful, it is messy for the reviewers.
> Actually, there are not so many logic changes in this new version.

OK, so this needs a fresh full review.  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.