Jeff King <peff@xxxxxxxx> writes: > As explained further in the commit message, "fetch" is robust to this, > because it does a real connectivity check and follow-on fetch before > writing anything it thinks it got via include-tag. So perhaps one could > argue that pack-objects is correct; include-tag is best-effort, and it > is the client's job to make sure it has everything it needs. And that > would mean the bug is in git-clone, which should be doing the > connectivity check and follow-on fetch. I think that is probably a more technically correct interpretation of the history. I think upgrading "best-effort" to "guarantee" like you did is a right approach nevertheless. I think the "best-effort" we initially did was merely us being lazy.