On Sun, 6 Nov 2016 04:57:03 -0500, timeless wrote: > Pulkit Goyal wrote: > > This patch does not exactly solve issue5228 but it results in a better > > If it doesn't solve the issue, should the issue be tagged in the commit summary? I think this fix is enough to say issue5228 is solved.