On Mon, Jul 18, 2016 at 4:01 PM, Sergey Aleynikov < sergey.aleynikov@gmail.com> wrote: > Commit 73949fca082fe50bf47755c5ffa328259057ae36 has never actually > made it into the 5.22 branch. > Is it possible to cherry-pick it for the next maint release (while > they are), as it's currently the only > thing that prevents Coro from compiling on 5.22? > I was also rather surprised when I discovered that, it would have expected them in 5.22.1. Leon