git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug report: AM 3-way patching fails with partial cloning

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 4, 2023, 22:02 UTC
Message-ID
<xmqqedln49nz.fsf@gitster.g>
In-Reply-To
<1e79047e-944c-0112-ffd0-ca52e31226c3@mschiffer.de>
Marius Schiffer <marius@mschiffer.de> writes:
> When applying patches with git am on a repository cloned with
> filter=blob:none, the patching sometimes fails when it can't find the
> required SHA1 information.
> Applying the same thing on a normal clone works.

This is very much expected, especially if your patches are not generated with --full-index option, because partial clones cannot on-demand request objects without knowing their full object names to the promissor remote. I do not offhand know if "am -3" codepath, if the full object name is available, is arranged to trigger lazy fetching of the objects, but nobody sane are sending patches with the --full-index option to begin with, so that is academic, I would say.

Previous: Marius Schiffer
Message 2 of 2 in “Bug report: AM 3-way patching fails with partial cloning”
  1. Marius SchifferJul 3, 2023
  2. Junio C HamanoJul 4, 2023

Read the whole thread, see it on lore, or plain text.

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