Daniel Svensson

See also https://github.com/flyway/flyway/issues/3550 Another way to disable specifically flyway, with whatever cost that may incur, is via: ```kotlin withType { notCompatibleWithConfigurationCache("because https://github.com/flyway/flyway/issues/3550") } ```

I'm still confused why you insist submitting merge commits in your PR. They add zero information to the change, just noise.

The absolutely easiest, as it's just four commits, would be to reset to upstream master and cherry-pick them one by one. slimes authorship would remain. But just a recommendation, looks...

Visual studio has supported opening cmake project natively for years, and cmake has been able to generate vsproj even longer. It's just noise in the repo and a way to...

fyi you don't need to close the PR over and over again, just forcepush to your branch to update it.

build breaks qvm target, q3lcc requires variables to be declared at start of block.

Pretty massive upgrade in many cases, any idea how it has been done? AI resampling? Feels like in some cases there's quite the added detail for it to be simply...

Humm... I was hoping that I had overridden that, but must have gotten lost over the years. But it sounds like a plausible reason. Would be nice to get the...

Usecase is to be able to present correct number of viewers at https://hub.quakeworld.nu/qtv/

@Xylemon @eukara it's christmas! plox merge!