{"thread":{"id":"16015","subject":"Older git version on the server","startedAt":"2008-10-22T20:33:01Z","lastAt":"2008-10-22T20:33:01Z","messageCount":1,"participants":["Diego Algorta"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"93722","messageId":"48FF8DFD.2060700@oboxodo.com","threadId":"16015","inReplyTo":null,"subject":"Older git version on the server","fromName":"Diego Algorta","fromEmail":"diego@oboxodo.com","sentAt":"2008-10-22T20:33:01Z","receivedAt":"2008-10-22T20:33:01Z","isPatch":false,"sender":{"key":"diego@oboxodo.com","avatar":null},"body":"Hi all,\n\n= Background\nWe are a team of 3 developers. Each one has his own clone from a central \npublic repo in our server where we all push and pull from (you can tell \nwe come from svn). We do deployments on production from that repo's \nmaster branch.\n\n= Problem\nWe recently started using git submodules and now we're facing a problem \nwhen switching between branches (git checkout) which have the same \nsubmodule but linked from different sources. Some google research says \nthe new \"git submodule sync\" feature may be the solution, but we can't \nuse a version newer than 1.5.6.1 on the server.\n\n= Question\nWould it be a problem for us to use 1.6.0.3 on our development \nenvironments and keep using 1.5.6.1 on the server to do the deployments?\n\nThank you!\n-- \nDiego Algorta - Web Developer & SysAdmin -\nhttp://www.oboxodo.com - http://diego.algorta.net\n"}]}