2023-03-29 16:33:15 +00:00
|
|
|
#!/bin/sh
|
|
|
|
|
set -e
|
|
|
|
|
|
2023-11-09 11:39:50 +00:00
|
|
|
SCRIPT_PATH=$(realpath "$0")
|
2023-11-09 14:25:59 +00:00
|
|
|
SCRIPT_DIR=$(dirname "${SCRIPT_PATH}")
|
|
|
|
|
GIT_DIR=$(git -C "$SCRIPT_DIR" rev-parse --show-toplevel)
|
2023-11-09 11:39:50 +00:00
|
|
|
cd $GIT_DIR
|
2023-03-29 16:33:15 +00:00
|
|
|
|
2023-11-09 11:39:50 +00:00
|
|
|
contrib/sparse-checkout/setup-sparse-checkout.sh
|
2023-03-29 16:33:15 +00:00
|
|
|
git submodule init
|
|
|
|
|
git submodule sync
|
2023-11-16 12:57:58 +00:00
|
|
|
# NOTE: do not use --remote for `git submodule update`[1] command, since the submodule references to the specific commit SHA1 in the subproject.
|
|
|
|
|
# It may cause unexpected behavior. Instead you need to commit a new SHA1 for a submodule.
|
|
|
|
|
#
|
|
|
|
|
# [1] - https://git-scm.com/book/en/v2/Git-Tools-Submodules
|
|
|
|
|
git config --file .gitmodules --get-regexp '.*path' | sed 's/[^ ]* //' | xargs -I _ --max-procs 64 git submodule update --depth=1 --single-branch _
|
