Re: [PATCH 4/8] d3d10/effect: Explicitly store rasterizer state variable.

[Matteo Bruni]

Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com>
---
This one (and similarly the following two, obviously) could have used
a mention in the commit subject or message about fixing
D3D10_EOO_CONST_INDEX rasterizer state settings. Any known game that's
affected by this?

BTW, this will need to be changed again to allow for
D3D10_EOO_VAR_INDEX (assuming that's possible for rasterizer state)
since the index is not known at parse time. It's a step in the right
direction though.