On 8/06/2014 11:40 AM, Kurt Roeckx via RT wrote: > On Sun, Jun 08, 2014 at 12:01:28AM +0200, Tim Hudson via RT wrote: >> Already fixed in the 1.0.1 stable branch so it is already included in >> 1.0.1h onwards and 1.0.1m is the current recommended version. > [...] >> Can you re-run parfait against the current release version of OpenSSL >> for that branch - i.e. 1.0.1m > It seems you have your branches mixed up. The latest version is > 1.0.1h. There is an also an 1.0.0m, but that's from an older > branch.
Opps - you are right - I did indeed mean *1.0.1h* ... 'm' is in the 1.0.0 branch - and I am requesting is for it to be run against the current 1.0.1 version not an older version - which was especially noticeable when it is pointing out an already resolved item. It is always a good idea to run any tools against the current release versions for a particular branch - and also handy to see the same reports against "master" so that the forward development version also gets items picked up - as it contains the latest not-yet-in-a-release code. For coverity we use "master" and "OpenSSL_1_0_1-stable" Tim. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
