summaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorDaniel P. Berrange <berrange@redhat.com>2017-10-27 10:49:58 +0100
committerDaniel P. Berrange <berrange@redhat.com>2017-11-06 11:05:12 +0000
commit37b5e74e28f4b3ee93c28eb0106a65e02521f48b (patch)
tree4c6c571cff454e8a03c2581b77467e6191f6c3b4 /MAINTAINERS
parentf62bbee55d503f639ee9498878ebf42ff4f4299a (diff)
downloadqemu-37b5e74e28f4b3ee93c28eb0106a65e02521f48b.tar.gz
build: don't fail if given a git submodule which does not exist
If going back in time in git history, across a commit that introduces a new submodule, the 'git-submodule.sh' script will fail, causing rebuild to fail. This is because config-host.mak contains a GIT_SUBMODULES variable that lists a submodule that only exists in the later commit. config-host.mak won't get repopulated until config.status is invoked, but make won't get this far due to the submodule error. This change makes 'git-submodule.sh' check whether each module is known to git and drops any which are not present. A warning message will be printed when any submodule is dropped in this manner. Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions