On Wed, 15 Mar 2017 at 07:39 <rahu...@swecha.net> wrote: > This patch is no longer required now as this issue has been fixed with > the new release 1.1.0 in upstream. >
Thanks for tracking / following up on this issue; I have been paying attention despite the silence from my side, and it is appreciated :) I'm planning to look at uploading the new release in the next few days; should be by the end of the weekend at the latest.
