Re: [PATCH v2 0/5] fetch: more optimizations for mirror fetches

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 1, 2022, 22:02 UTC
Message-ID: <xmqqv8wxnxf6.fsf@gitster.g>
In-Reply-To: <cover.1646127015.git.ps@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> this is another patch series with the aim to speed up mirror fetches. It
> applies on top of e6ebfd0e8c (The sixth batch, 2022-02-18) with
> 3824153b23 (Merge branch 'ps/fetch-atomic' into next, 2022-02-18) merged
> into it to fix a conflict.

Thanks for clearly describing a base. Except that a merge on 'next' (e.g. 3824153b23) is not what we want a new topic to depend on; use the tip(s) of individual topic(s), i.e. 583bc419 (fetch: make `--atomic` flag cover pruning of refs, 2022-02-17), instead.

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