s9y/additional_plugins — comment on commit 3241bcb3156a9cc193adff968f09ba039bb85cb0
File:  line 0
By brockhaus:

We (garvin, mattsches, yellowled) talked a lot about this last night on twitter, I didn't think about, that there are more involved, of course, sorry.

This happened:
mattsches did a commit, that set this repo in a state he had on some of his branches. I don't know _exactly_ what he did, but his commit was wrong (as you can see here, he wanted to change one file but changed all files).

I did reset the repo to the state it was before mattsches committed (as my local repo was on that state, a forced push was enough). The state before was 6a826e2 and yes, it was some days old (nothing happened in the meantime in this repo).

A forced push is a bad thing normally (if someone else pulled in the meantime and made some changes on the top of this state). But as we did it very short after mattsches did his commit,nobody should get in trouble I think.