Comment 5 for bug 395731

I just spent a happy three hours fixing our main repository *again*. A developer in a hurry has committed and merged code without proper rules configuration. This caused a commit which helpfully changed all 16000 files in the repository. I was lucky in that there were not too many commits and merges after it or I would have been forced to re-create our repositories from scratch *again*, losing all history in the process. Eye, needle, things like that.

In addition, I look forward to a nice Monday morning where I can help every developer to get things right on their local workstations.

I get a bit frustrated that it is this easy to destroy a main repository.

Is there any way to get this thing fixed faster? An easy way to handle this would be to just accept a "rules" file in the branch root somewhere (".bzrrules"). Would a patch doing that be accepted?