Stefan Beller <sbeller <at> google.com> writes: > > On Thu, May 5, 2016 at 12:20 PM, Loet Avramson <loet <at> forter.com> wrote: > > It happened on 2.8.1, also reproducible on 2.8.2. > > Haven't had the time to dive deeper into the code but my guess is that > > relative_path() returns different results in those 2 cases or maybe > > the way git-submodule.sh handles it. > > > > Then you found a new bug, congratulations. ;) > Thanks for reporting. > > The shell script uses relative_path() only for displaying paths, > not for writing them to the .git file. > > it really boils down to different environments > "git submodule update --init --recursive" is called from > (either manually or from `git clone`). > > Apart from that there are no immediate bells ringing, > are you doing any weird stuff with the file system (soft/hard > links) ? > > Thanks, > Stefan >
Hi, sorry to awake an old thread. Has this been fixed? In which git version? It's hitting me on git version 2.7.4 (Apple Git-66) (default git client on OS X 10.11.5 (15F34)). I think all submodule .git files should contain relative paths. Otherwise, duplicating or moving the cloned repository folder breaks the submodules. Best, Ricardo -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
