> So, if I understand correctly, then we can mark the version posted by
> you upthread [1] which includes a test along with Kyotaro's fix can be
> marked as Ready for committer. If so, then please change the status
> of patch accordingly.
Patch moved to next CF 2016-11, still with status "ready for committer".
IMO, this thread has reached as conclusion to use this patch to
address the problem reported:
CAB7nPqTv5gmKQcNDoFGTGqoqXz2xLz4RRw247oqOJzZTVy6-7Q(at)mail(dot)gmail(dot)com
--
Michael