On 11-06-28 07:02 PM, Fredrik Gustafsson wrote: > > [ ... ] > > Serverside, we cannot guarantee that all submodules are reachable, they > might be on different servers, maybe not even connected to eachothers. Even > if they are connected this would requiring network traffic. Making this check > an even bigger performance killer. This check is not supposed to guarantee a > sane server-repo (that would be much harder) and therefore this check is > "overkill" to have on the server-side. Client side we always have all > information needed for this. > > Note the problem: > "Prevent the developer of pushing a superrepo that has submodule > (commits) only locally avaliable" > > That's the problem we're trying to solve, NOT: > > "Prevent the developer of pushing a superrepo that has submodule > (commits) not avaliable for an other developer" > > The second problem is just too complex and too slow to solve in a generic > way. Fair enough. So my only remaining concern is that using "push -f" to override the check is too much. I'd rather see a different option control this. Maybe --ignore-submodules? (I think it'd be fine if -f implied --ignore-submodules.) M. -- 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