29 Sep
2013
29 Sep
'13
9:19 a.m.
Jakob Hirsch wrote:
On 28.09.2013 16:44, Alan DeKok wrote:
This looks quite strange to me... I've pushed a fix. Please try the v2.x.x branch on git. If it's OK, we'll release 2.2.1 on Monday.
Thanks, but it doesn't seem to fix it:
OK. I had a similar test case. Some code searching later... it turns out that the v2.2.1 (and previous) code worked sort of by accident. There was an underlying bug which was highlighted by the new code. i.e. everything should work like X. But the "update" sections didn't. So... there was a bug. The old code had many special cases, and worked almost by magic. It's nice that it's gone. Your test case should now work. Alan DeKok.