summaryrefslogtreecommitdiffstats
path: root/contrib/persistent-https
diff options
context:
space:
mode:
authorNasser Grainawi <nasser.grainawi@oss.qualcomm.com>2026-03-03 15:40:44 -0800
committerJunio C Hamano <gitster@pobox.com>2026-03-03 18:00:43 -0800
commit3b5fb32da836f5aead1cef319bc3e0a9b975ea35 (patch)
tree6b21ac32451adcd65ae382f4be021a52c08bc217 /contrib/persistent-https
parent1faf5b085a171f9ba9a6d7a446e0de16acccb1dc (diff)
downloadgit-3b5fb32da836f5aead1cef319bc3e0a9b975ea35.tar.gz
git-3b5fb32da836f5aead1cef319bc3e0a9b975ea35.zip
submodule: fetch missing objects from default remote
When be76c21282 (fetch: ensure submodule objects fetched, 2018-12-06) added support for fetching a missing submodule object by id, it hardcoded the remote name as "origin" and deferred anything more complicated for a later patch. Implement the NEEDSWORK item to remove the hardcoded assumption by adding and using a submodule helper subcmd 'get-default-remote'. Fixing this lets 'git fetch --recurse-submodules' succeed when the fetched commit(s) in the superproject trigger a submodule fetch, and that submodule's default remote name is not "origin". Add non-"origin" remote tests to t5526-fetch-submodules.sh and t5572-pull-submodule.sh demonstrating this works as expected and add dedicated tests for get-default-remote. Signed-off-by: Nasser Grainawi <nasser.grainawi@oss.qualcomm.com> Reviewed-by: Jacob Keller <jacob.keller@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/persistent-https')
0 files changed, 0 insertions, 0 deletions