Junio C Hamano <gitster@xxxxxxxxx> writes: > That is exactly what I said in the parentheses above, isn't it? The > danger of "--force" does not have anything to do with which branches > are pushed. I disagree. A user may use --force because he has good reason to think that a branch hasn't been been touched by others, but it's much harder to guarantee that all branches haven't been touched. > That does not change the conclusion that current is more suitable > for shared repository workflow and matching is more (not "equally to > current") suitable for publishing repository workflow, and we have a > way for user to tell Git which one is being used in a particular > project exactly for that purpose. We're not talking about the same thing. You're talking about how _appropriate_ a value is, and I'm mentionning how _dangerous_ it can be. And regardless of the danger, if I look around me, I see almost only people working with shared archives, and a few projects (including Git, obviously) using the "one commiter per repository" workflow (I teach Git to 200 students and several colleagues every year, I've tried teaching the "one public repository per developer" and it was a complete disaster). I really think the default should help these people. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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