{"thread":{"id":"10080","subject":"Submodule idea","startedAt":"2007-09-29T19:04:50Z","lastAt":"2007-09-29T19:04:50Z","messageCount":1,"participants":["Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"54357","messageId":"Pine.LNX.4.64.0709291442430.5926@iabervon.org","threadId":"10080","inReplyTo":null,"subject":"Submodule idea","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-09-29T19:04:50Z","receivedAt":"2007-09-29T19:04:50Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"I *think* that it would be a great benefit if \"git submodule update\" would \nleave you on a branch if (a) you were on that branch before, and (b) \npulling on that branch would update it to the commit that the superproject \nspecifies for that submodule.\n\nOr maybe there should be a \"git submodule fetch\" which fetches from the \nremote, and replaces FETCH_HEAD with the superproject's index entry, and \n\"git submodule pull\" would merge it? (With the model being that the entry \nin the superproject is an additional remote that you both track and \npublish to)\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}