| commit | 250ab24ab3a35d5857855a2e00483dcd8867fdca | |
| author | Heiko Voigt <hvoigt@hvoigt.net> | |
| Wed, 16 Nov 2016 15:11:07 +0000 (16 16:11 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 16 Nov 2016 19:13:58 +0000 (16 11:13 -0800) | ||
| tree | eff16729348b57555474af3741b448fb0424feb1 | treesnapshot (tar.gz zip) |
| parent | 5b6607d23f8a262e1c0ede954f0477664934eed8 | commitdiff |
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>
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>
| submodule.c | diffblobblamehistory |