Re: [tim-janik/beast] A few bsefcompare cleanups for cppcheck/scan-build issues (#135)

2020-01-13 Thread Tim Janik via beast
Closed #135.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/135#event-2943907797___
beast mailing list
beast@gnome.org
https://mail.gnome.org/mailman/listinfo/beast


Re: [tim-janik/beast] A few bsefcompare cleanups for cppcheck/scan-build issues (#135)

2020-01-13 Thread Tim Janik via beast
Closed by b85e36ed31352f9e74e3e1e272ad9c9243a7646b

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/135#issuecomment-573754416___
beast mailing list
beast@gnome.org
https://mail.gnome.org/mailman/listinfo/beast


[tim-janik/beast] A few bsefcompare cleanups for cppcheck/scan-build issues (#135)

2019-12-28 Thread Stefan Westerfeld via beast
The first commit really just cleans up the code as suggested by cppcheck, 
however the second commit fixes an actual bug in the max similarity 
computation, although for almost everybody the fix is irrelevant.
You can view, comment on, or merge this pull request online at:

  https://github.com/tim-janik/beast/pull/135

-- Commit Summary --

  * TOOLS: bsefcompare: minor code cleanups as recommended by cppcheck
  * TOOLS: bsefcompare: fix broken maximum calculation (found by scan-build)

-- File Changes --

M tools/bsefcompare.cc (32)

-- Patch Links --

https://github.com/tim-janik/beast/pull/135.patch
https://github.com/tim-janik/beast/pull/135.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/135
___
beast mailing list
beast@gnome.org
https://mail.gnome.org/mailman/listinfo/beast