Mike,
I don't remember it breaking win32. As I remember it, it was committed the day before 0.4.10 , which wasn't appropriate for a patch like this.
Please accept my apologies, you're correct it didn't break anything, just wasn't appropriate so close to a release.
Paul