Hi, On Mon, 7 Jul 2008, Avery Pennarun wrote: > 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? It updates the tracking branches. And guess what I use the tracking branches for? Yes, to track other people's changes. It would wreck my state. Anyway, fetch is wrong, wrong, wrong, if all you want to do is see the _state_ of your submodule. If that state is that the superproject has a commit that the submodule knows nothing about, then that is _exactly_ what needs to be reported. Don't play cute games, Dscho -- 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
