aboutsummaryrefslogtreecommitdiff
path: root/git-submodule.sh
diff options
context:
space:
mode:
authorHeiko Voigt <hvoigt@hvoigt.net>2016-11-16 16:11:07 +0100
committerJunio C Hamano <gitster@pobox.com>2016-11-16 11:13:58 -0800
commit250ab24ab3a35d5857855a2e00483dcd8867fdca (patch)
treeeff16729348b57555474af3741b448fb0424feb1 /git-submodule.sh
parent5b6607d23f8a262e1c0ede954f0477664934eed8 (diff)
downloadgit-250ab24ab3a35d5857855a2e00483dcd8867fdca.tar.gz
git-250ab24ab3a35d5857855a2e00483dcd8867fdca.tar.xz
submodule_needs_pushing(): explain the behaviour when we cannot answer
When we do not have commits that are involved in the update of the superproject in our copy of submodule, we cannot tell if the remote end needs to acquire these commits to be able to check out the superproject tree. Explain why we answer "no there is no need/point in pushing from our submodule repository" in this case. Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-submodule.sh')
0 files changed, 0 insertions, 0 deletions