Sonic CD [NPEB00787]

c01b5fb? That would be this issue then... I will reopen that issue.

Also, you didn't have to test all revisions. What you do is for example, let's say we have 100 revisions, 1,2,3... 99,100.

You test rev. 1 and confirm the game is broken. Then you test rev. 100 and confirm the game works. Then you test rev. 50. If the game works in rev. 50 you only need to look at revisions 2-49, because it had to break there, and not before it. If the game doesn't work you only need to look at revisions 51-99, again because you already know everything after 50 is also broken.

So let's say the game didn't work. You again test some revision in the middle of 51-99, like 75, and keep doing this, drastically speeding up the test process.

Just to be clear, git has a tool specifically for this: git bisect.