Message238505
I'm attaching second version of the patch. It now contains link to this bug and a more real test case according to suggestion from the review.
One of the reviews of first patch version mentioned that there should be a better explanation of how this issue can be provoked. I think that the test shows it nice and there's no need to explain it in greater detail. Also, the comment references this bug, where anyone can find the explanation. (Fix for #18879 fixes pretty much the same in a different method and has very similar comment, so I think this should be fine.) |
|
Date |
User |
Action |
Args |
2015-03-19 12:50:36 | bkabrda | set | recipients:
+ bkabrda, georg.brandl, ncoghlan, ethan.furman, serhiy.storchaka, sYnfo, wolma |
2015-03-19 12:50:36 | bkabrda | set | messageid: <1426769436.7.0.284440792953.issue23700@psf.upfronthosting.co.za> |
2015-03-19 12:50:36 | bkabrda | link | issue23700 messages |
2015-03-19 12:50:36 | bkabrda | create | |
|