On 7/7/08, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > On Mon, 7 Jul 2008, Avery Pennarun wrote: > > Thus, I'd say the best fix would be to find a way to have "git pull" or > > "git fetch" in the supermodule also do a fetch in the submodule. > > Noooooo! > > If I am actively working on the submodule, the supermodule has _no > business_ trying to wreck my state. Hmm... how does doing a fetch wreck your state? I thought fetch was supposed to be a pretty harmless operation. We're not talking about doing a "git submodule update" automatically (which would be deadly, albeit only because "git submodule update" is so destructive at present). All I'm suggesting is, when doing a "git fetch" in the supermodule, simply do a "cd submodule && git fetch" automatically. Probably should be optional, but seems like it could make sense for most uses, and avoids the (probably much more common) annoyance of fetching in the supermodule and taking my laptop on the road, only to find out that I don't actually have all the objects I need. On the other hand, for my own workflow I'm shifting increasingly toward having all my "submodules" share a single repo anyway, in which case fetching in the supermodule *would* automatically fetch all my relevant submodule objects too. Have fun, Avery -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
