summaryrefslogtreecommitdiff
path: root/config/submodule/coreboot/coreboot413
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2024-05-24 17:50:42 +0100
committerLeah Rowe <leah@libreboot.org>2024-05-24 18:58:48 +0100
commit1cb255e8be3988980446d61da8d99ab035a9f909 (patch)
tree6b458dc8fe2fd55cea0a20c949e0e213b4083dda /config/submodule/coreboot/coreboot413
parent5d87eea77c5a6db9263f08052700bd39b7c2d4c5 (diff)
git.sh: allow finer control of git submodules
in each submodule configuration directory, a module.cfg file can now be provided. in it, the user can specify two repository links (main and backup) and a revision, like so: subrepo="repo link goes here" subrepo_bkup="backup repo link goes here" subrev="git revision id goes here" additionally: in the *main* project directory for the submodules, a module.list file can be provided. example entries: 3rdparty/vboot 3rdparty/libgfxinit if the module.list file is provided, only those submodules will be downloaded. this can be combined with the module.cfg files, if you wish, but it's optional. you can mix and match. example locations: multi-tree project: config/submodule/coreboot/default/module.list config/submodule/coreboot/default/vboot/module.cfg single-tree project: config/submodule/flashprog/module.list config/submodule/flashprog/foo/module.cfg *no* configuration files have been provided, in this commit, which means that the current behaviour is maintained. follow-up commits will absolutely configure the submodules. this is being done to reduce the number of modules downloaded, because we don't use most of the coreboot submodules that are downloaded, thus wasting bandwidth and the releases are also much bigger than necessary. Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'config/submodule/coreboot/coreboot413')
0 files changed, 0 insertions, 0 deletions