IceDreamer wrote:Xinnony your problem solving is ready to go in!
All Chris did was take some of it from your PR and split it up for you
IceDreamer's right, you know: PRs #373 and #374 were spawned from the code review I did on your PR. #374 even includes one of your commits verbatim (unfortunately much of the rest ended up being rewritten, but with significant inspiration from your earlier work).
Xinnony wrote:I try to solve some problems, but we still shit above me again.
You can request on github and with a little luck instead of gun the script it will be be fixed.
File a bug report, either on GitHub or on the "FAF tech support" forum here (from which it'll usually find its way to GitHub within a day), and it'll get the attention it deserves. I think we've got all the current regressions in the tracker now (and several of them fixed in trunk: hooray!)
Throwing a tantrum on the forum or, (as you did a few hours ago) closing all your bug reports on GitHub is not helpful; it just makes the rest of the team have to take time away from doing useful work to deal with it.
If you don't think Sheeo is doing an adequate job of reviewing patches, review them yourself. That is literally what GitHub is *for*. Go through them with a fine toothcomb and pick out every minuscule mistake you can find. You'd be contributing usefully to the development of the project, helping to keep the regression rate down, and helping to educate other contributors about subtleties they may have missed.
When I did this to you, you seemed to misunderstand and got angry.