Thomas Morley <[email protected]> writes: > Below the (shortened) code where I was hit by #34 for the very first > time (it was for 2.12.3 back in 2011).
I'll check. > BTW, which of your currently proposed MRs should I apply to test #34 > myself, !3153 or more? It's all consolidated into !3153 at the current point of time. Finding cases where it doesn't help is of course interesting for figuring out whether further improvements are warranted and will not necessarily halt the pipeline. In contrast, finding cases where previously working code (no matter how many workarounds are in there) stops working is of course the most important thing in order to catch problems before they reach every user. Well, every user of the current unstable release at least. If you feel you want more time for that, holler in time so that !3153 will not get advanced to Patch-push or when it does, that I will not act on it. -- David Kastrup
