Skip to content

Conversation

DanConwayDev
Copy link

Stop throwing error when requesting oids from a git server that doesn't explicitly advertise that capability.

The overwhelming majority of git servers will serve this request even when they don't advertise this capability, e.g. git-http-backend.

For many years, the git reference implementation has assumed servers have this capability even when allow-tip-sha1-in-want or allow-reachable-sha1-in-want isnt included in
git-upload-pack-advertisement, e.g. with git fetch <remote> <oid>.

closes #7078

Stop throwing error when requesting oids from a git server that
doesn't explicitly advertise that capability.

The overwhelming majority of git servers will serve this request
even when they don't advertise this capability, e.g. git-http-backend.

For many years, the git reference implementation has assumed
servers have this capability even when `allow-tip-sha1-in-want` or
`allow-reachable-sha1-in-want` isnt included in
`git-upload-pack-advertisement`, e.g. with `git fetch <remote> <oid>`.

closes libgit2#7078
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: git_remote_download returns invalid if allow-tip-sha1-in-want not advertised
1 participant