From: Junio C Hamano <gitster@pobox.com>
To: Marius Schiffer <marius@mschiffer.de>
Cc: git@vger.kernel.org
Subject: Re: Bug report: AM 3-way patching fails with partial cloning
Date: Tue, 04 Jul 2023 15:02:56 -0700 [thread overview]
Message-ID: <xmqqedln49nz.fsf@gitster.g> (raw)
In-Reply-To: <1e79047e-944c-0112-ffd0-ca52e31226c3@mschiffer.de> (Marius Schiffer's message of "Mon, 3 Jul 2023 18:46:45 +0200")
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.
prev parent reply other threads:[~2023-07-04 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 16:46 Bug report: AM 3-way patching fails with partial cloning Marius Schiffer
2023-07-04 22:02 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqedln49nz.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=marius@mschiffer.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).