Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> writes: > Thinking more about it, we try to encourage a workflow where locally > history may be rewritten a lot, and distribution points fast-forward > only. We have defaults and settings to discourage (pushes to checked out > branches and) non-ff pushes, for example. So I think the above change is > pretty much in line with that reasoning. Agreed. It's not only a security thing, it's also about teaching/encourraging workflows. By asking users to explicitely say "yes, I know, this branch can be rewond", we also ask them to think about it before making a mistake. That said, enabling the check by default may also become painful. I'd vote for a configuration option, defaulting to the current behavior for now. Then we can try living with it for a while and see how painful it is. -- 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