-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/01/2014 16:41, Christopher Schultz wrote:
> Mark,
>
> On 1/17/14, 11:35 AM, Christopher Schultz wrote:
>> Mark,
>>
>> On 1/16/14, 6:54 PM, Mark Thomas wrote:
>>> It has been a while since the last 6.0.x release so I plan to
>>> tag 6.0.38 tomor
Mark,
On 1/16/14, 6:54 PM, Mark Thomas wrote:
> It has been a while since the last 6.0.x release so I plan to tag 6.0.38
> tomorrow (if all goes well). There are a couple of simple patches in the
> status file that I'd like to include in the tag. Votes welcome.
I'd like to squeeze-in a patch for
Mark,
On 1/17/14, 11:35 AM, Christopher Schultz wrote:
> Mark,
>
> On 1/16/14, 6:54 PM, Mark Thomas wrote:
>> It has been a while since the last 6.0.x release so I plan to tag 6.0.38
>> tomorrow (if all goes well). There are a couple of simple patches in the
>> status file that I'd like to includ
On 17/01/2014 02:30, Rob Sanders wrote:
> Would it be worth waiting to have the RHEL6/FIPS stuff looked at - at least
> to the point of deciding if the issue should involve fixes to both TC and TCN
> or be limited to TCN only?I posted Monday and earlier today about it.
> I believe the minim
Would it be worth waiting to have the RHEL6/FIPS stuff looked at - at least to
the point of deciding if the issue should involve fixes to both TC and TCN or
be limited to TCN only?I posted Monday and earlier today about it.
I believe the minimal patch to resolve the issue would involve TCN
