projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: 9cbd27b 6eafa6d)
Merge branch 'jl/maint-1.7.10-recurse-submodules-with-symlink'
authorJunio C Hamano <gitster@pobox.com>
Sun, 22 Jul 2012 19:55:47 +0000 (12:55 -0700)
committerJunio C Hamano <gitster@pobox.com>
Sun, 22 Jul 2012 19:55:48 +0000 (12:55 -0700)
commit15b3c82cbb345c890400119134fb9709790696d8
tree8afe28b48bb2f23dd5b0d364b186a102ae73b0ddtree | snapshot
parent9cbd27b19a2df0484fb1f3a4a227abdbeab3c23dcommit | diff
parent6eafa6d096ce6b0ae20e4c0fbb248958559daf64commit | diff
Merge branch 'jl/maint-1.7.10-recurse-submodules-with-symlink'

When "git submodule add" clones a submodule repository, it can get
confused where to store the resulting submodule repository in the
superproject's .git/ directory when there is a symbolic link in the
path to the current directory.

* jl/maint-1.7.10-recurse-submodules-with-symlink:
  submodules: don't stumble over symbolic links when cloning recursively
git-submodule.sh diff1 | diff2 | blob | history
Git—the stupid content tracker