On 03/04/16 22:32, Andy Carter wrote: > On Friday 18 Mar 2016 21:49:49 Johan Ström wrote: >> I've patched OWNet.pm in master now, to not send a null-terminated >> payload. > Sorry to come back to this one but I wonder if I could suggest/request a human > readable version no. or date stamp in OWNet.pm, perhaps even a comment to use > with 2.9p5 and later > > At present it is difficult for many to see the slight differences between > versions - and quite important as there seem to be many distros including > older versions of owfs that may require current OWNet.pm This information is present in the git log, and more importantly, the release notes when we do the next release. Then users at least can see "oh this new version has this fixed, i should use that". Just picking out random files from a newer version is generally not recommended, and in this case possibly not even working (since the protocol changed).
If every single bug was commented in the code, it would become a lot of comments.. :) The fact that a lot of distros lags behind is another problem though.. Johan ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
