Looking for a few old windows builds

[[Unknown]]

Well, what it means is there are actually multiple -533's. Here's how it works:

0.7-532
-> [Unknown] starts working on GPU signals.
-> raven02 starts working on pause screen options.

The "0.7-532" is "# of commits since 0.7." If both me and raven02 commit at this point, we don't have each other's changes yet, so we're BOTH at 533 (even though my 533 is very different from his 533.)

Anyway, let's say that we both do 3 commits That means we're both at 0.7-535.

Now we both submit pull requests. Henrik merges raven02's pull first, then mine. Here's what happens:
0.7-532 (was there before.)
0.7-533 raven02's first commit.
0.7-534 raven02's second commit.
0.7-535 raven02's third commit.
0.7-536 "merge" commit (in this case does nothing.)
0.7-533 [Unknown]'s first commit - DOES NOT INCLUDE raven02's commits.
0.7-534 [Unknown]'s second commit - DOES NOT INCLUDE raven02's commits.
0.7-535 [Unknown]'s third commit - DOES NOT INCLUDE raven02's commits.
0.7-540 "merge" commit (splices the two separate pulls together.)

As you see, there were a total of 8 commits (from 533 - 540), but they aren't numbered linearly.

I know it's a bit complicated but maybe that makes some sense. Anyway, point is that if my 533 broke something, then if you tested raven02's 534 and it worked, that wouldn't tell you that my 533 is innocent.

This is why git comes with a "bisect" feature, which is awesome. Unfortunately, when you're downloading builds, it's harder to get this, so you have to be careful when the numbers get close together.

-[Unknown]