git.99rst.org / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: cf22247 c3749f6)
Merge branch 'sb/fix-fetching-moved-submodules'
authorJunio C Hamano <redacted>
Thu, 28 Jun 2018 19:53:34 +0000 (12:53 -0700)
committerJunio C Hamano <redacted>
Thu, 28 Jun 2018 19:53:34 +0000 (12:53 -0700)
commit085d2abf57be3e424cad0b7dc8c27fe41921258e
tree758920947d1b46faf51fbfd963471c12ef5aa915tree | snapshot
parentcf22247b631ab7cdfe01289917583f84dfea6f32commit | diff
parentc3749f6e597a7b8140181fa5efc95f3f08595f8ccommit | diff
Merge branch 'sb/fix-fetching-moved-submodules'

The code to try seeing if a fetch is necessary in a submodule
during a fetch with --recurse-submodules got confused when the path
to the submodule was changed in the range of commits in the
superproject, sometimes showing "(null)".  This has been corrected.

* sb/fix-fetching-moved-submodules:
  t5526: test recursive submodules when fetching moved submodules
  submodule: fix NULL correctness in renamed broken submodules
git clone https://git.99rst.org/PROJECT