fetch/pull: Don't recurse into a submodule when commits are already present
commitc16c3e40b5908ecf28be12b1caf266c7ab8de3c6
authorJens Lehmann <Jens.Lehmann@web.de>
Sun, 6 Mar 2011 22:12:58 +0000 (6 23:12 +0100)
committerJunio C Hamano <gitster@pobox.com>
Wed, 9 Mar 2011 21:10:35 +0000 (9 13:10 -0800)
tree9ce602aebbccf20d66dd73d10b613d85bead1988
parentbf42b384058ee2b34f587426d0788353ffa9012a
fetch/pull: Don't recurse into a submodule when commits are already present

When looking for submodules where new commits have been recorded in the
superproject ignore those cases where the submodules commits are already
present locally. This can happen e.g. when the submodule has been rewound
to an earlier state. Then there is no need to fetch the submodule again
as the commit recorded in the newly fetched superproject commit has
already been fetched earlier into the submodule.

Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/fetch-options.txt
submodule.c
t/t5526-fetch-submodules.sh