Hilco Wijbenga <hilco.wijbenga@xxxxxxxxx> writes: >> Some ways you can prevent it from happening again: >> (1) setting your canonical repo config to deny non-ff, and deny deletes: >> [receive] >> denyDeletes = true >> denyNonFastforwards = true > > I would *really* like to do that but I need access to the server for > that, right? Unfortunately, we use Unfuddle and that means no such > access. So no server config changes and no Git hooks. receive.denyNonFastforwards is a reasonable thing to ask for projects with a shared repository workflow, so I suspect hosting service providers may want to race adding support for it to win customers. Have you asked them? -- 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