{"thread":{"id":"28173","subject":"'git submodule update' w/ .gitmodules 'update=merge' behaves differently on git 1.7.6 vs 1.7.2.5","startedAt":"2011-08-20T04:19:21Z","lastAt":"2011-08-20T20:16:54Z","messageCount":2,"participants":["nUxi Codes"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"173909","messageId":"CAD7xuUmtndhbWz7H0uQJ3gkbqurBGOsK8ATx6og9VifS6kc9fw@mail.gmail.com","threadId":"28173","inReplyTo":null,"subject":"'git submodule update' w/ .gitmodules 'update=merge' behaves differently on git 1.7.6 vs 1.7.2.5","fromName":"nUxi Codes","fromEmail":"code@nuxi.name","sentAt":"2011-08-20T04:19:21Z","receivedAt":"2011-08-20T04:19:21Z","isPatch":false,"sender":{"key":"code@nuxi.name","avatar":null},"body":"I have a repository with a submodule configured.\nIn .gitmodules, the \"update = merge\" option is set for the submodule.\nI am cloning the repo down from, for example, GitHub.\nAfter cloning the parent repo down, I run a:\n\n    git submodule init\n    git submodule update\n\nWith git 1.7.2.5 from Squeeze, the resulting submodule repo is\nunexpectedly bare.  The contents aren't there. 1.7.2.5 is printing:\n\n    ... (git clone) ...\n    user@oldhost:~/parentdir$ git submodule init\n    Submodule 'mysubmodule' (git://github.com/user/submodule.git)\nregistered for path 'submoduledir'\n    user@oldhost:~/parentdir$ git submodule update\n    Cloning into submoduledir...\n    remote: Counting ....(skipping the obvious).... deltas: 100%\n(###/###), done.\n    Already up-to-date.\n    Submodule path 'submodule': merged in\n'450e1a4ca6705c193d92b34e247fb63d32416c81'\n    user@oldhost:~/parentdir$ ls submodule\n    .git\n    user@oldhost:~/parentdir$\n\n\nWith git 1.7.6 built on FreeBSD, the contents of the submodule are\nthere.  It is not bare.\n\n    ... (Same) ...\n    Submodule path 'bundle/pathogen': checked out\n'450e1a4ca6705c193d92b34e247fb63d32416c81'\n    user@newhost:~/parentdir$ ls submodule\n    .git                            Stuff                   Things\n     .gitignore ...etc...\n    user@newhost:~/parentdir$\n\n\nWhy the difference?  Was this fixed intentionally?\nIf so, why hasn't Debian backported the fix?  It breaks a very common\nway of setting things up.\n"},{"id":"173938","messageId":"CAD7xuU=qiVrs6f3eLSJaGiO80e=hL8acESKzJnMbC4NMtTvZag@mail.gmail.com","threadId":"28173","inReplyTo":"CAD7xuUmtndhbWz7H0uQJ3gkbqurBGOsK8ATx6og9VifS6kc9fw@mail.gmail.com","subject":"Re: 'git submodule update' w/ .gitmodules 'update=merge' behaves differently on git 1.7.6 vs 1.7.2.5","fromName":"nUxi Codes","fromEmail":"code@nuxi.name","sentAt":"2011-08-20T20:16:54Z","receivedAt":"2011-08-20T20:16:54Z","isPatch":false,"sender":{"key":"code@nuxi.name","avatar":null},"body":"On 20 August 2011 00:19, nUxi Codes <code@nuxi.name> wrote:\n> Was this fixed intentionally?\n\nApparently, it was-\nhttp://permalink.gmane.org/gmane.comp.version-control.git/169364 .\n\n> If so, why hasn't Debian backported the fix [to stable]?  It breaks...\n\nThis question remains.\n"}]}