{"thread":{"id":"13249","subject":"submodules and branches","startedAt":"2008-04-25T00:41:42Z","lastAt":"2008-04-25T00:41:42Z","messageCount":1,"participants":["Stephen Hemminger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"75163","messageId":"20080424174142.5dbb6ae3@speedy","threadId":"13249","inReplyTo":null,"subject":"submodules and branches","fromName":"Stephen Hemminger","fromEmail":"stephen.hemminger@vyatta.com","sentAt":"2008-04-25T00:41:42Z","receivedAt":"2008-04-25T00:41:42Z","isPatch":false,"sender":{"key":"stephen.hemminger@vyatta.com","avatar":null},"body":"Our CM team likes to use both submodules and branches and it doesn't\nalways work cleanly.  Some examples:\n\n1. The new release on branch \"next_release\" adds a submodule, but then the\nsubmodule shows up on all branches including the production branch.\n\n2. For next release on branch \"next_release\" a submodule was renamed by\nmoving the target directory, but now git submodule update makes two copies.\n\nGit generally does a good job of tracking renames and deletions, so the fact\nthat submodules leave stuff behind is surprising.\n"}]}