{"thread":{"id":"23935","subject":"submodule questions","startedAt":"2010-05-28T20:45:10Z","lastAt":"2010-05-28T20:45:10Z","messageCount":1,"participants":["Cliff Brake"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"142507","messageId":"AANLkTilWHMkf5e7PBgnrI1tsGUYOldnv6AWKU3GG02u2@mail.gmail.com","threadId":"23935","inReplyTo":null,"subject":"submodule questions","fromName":"Cliff Brake","fromEmail":"cliff.brake@gmail.com","sentAt":"2010-05-28T20:45:10Z","receivedAt":"2010-05-28T20:45:10Z","isPatch":false,"sender":{"key":"cliff.brake@gmail.com","avatar":null},"body":"Hello,\n\nI've been trying to understand git submodules.\n\n1) What is the purpose for the submodule lines in .git/config?\n2) should 'git submodule sync' update the .git/config with submodule\ninfo, or what exactly does 'git submodule sync' do?\n\nI read the following:\nhttp://therealadam.com/archive/2008/05/08/changing-git-submodule-urls/\n The author claims that:\n\n    * Fork/create your own version of the submodule in question\n    * Change the URL for the submodule in .git/config and .gitmodules\n    * Cross your fingers and hope for the best\n\nDoes not work, but in my experience it does.  On machine #1, I did the\nfollowing:\n\n1) created a new branch in the submodule dir, pushed the changes to a new repo.\n2) modified .gitmodules to point to the new repo\n3) push the changes in the parent repo\n\nOn Machine #2:\n\n1) git pull\n2) git submodules sync\n3) git submodules update\n\nEverything seemed to work.  However, the .git/config submodule entry\nstill points to the old location, even though 'git submodule update'\nseemed to work.  Hence my confusion about what .git/config submodule\nentries are for.\n\nThanks,\nCliff\n"}]}