On 07/17/2012 08:52 PM, Rob Crittenden wrote:
When determining whether a member is direct or indirect we were not
doing a case-insensitive comparison which led to marking a member as
both direct and indirect (in a test case no less).
This patch fixes the comparison and the test.
rob
When
Petr Viktorin wrote:
On 07/17/2012 08:52 PM, Rob Crittenden wrote:
When determining whether a member is direct or indirect we were not
doing a case-insensitive comparison which led to marking a member as
both direct and indirect (in a test case no less).
This patch fixes the comparison and the
On 07/19/2012 03:07 PM, Rob Crittenden wrote:
Petr Viktorin wrote:
On 07/17/2012 08:52 PM, Rob Crittenden wrote:
When determining whether a member is direct or indirect we were not
doing a case-insensitive comparison which led to marking a member as
both direct and indirect (in a test case no
Petr Viktorin wrote:
On 07/19/2012 03:07 PM, Rob Crittenden wrote:
Petr Viktorin wrote:
On 07/17/2012 08:52 PM, Rob Crittenden wrote:
When determining whether a member is direct or indirect we were not
doing a case-insensitive comparison which led to marking a member as
both direct and
On 07/19/2012 01:35 PM, Rob Crittenden wrote:
Petr Viktorin wrote:
On 07/19/2012 03:07 PM, Rob Crittenden wrote:
Petr Viktorin wrote:
On 07/17/2012 08:52 PM, Rob Crittenden wrote:
When determining whether a member is direct or indirect we were not
doing a case-insensitive comparison which
When determining whether a member is direct or indirect we were not
doing a case-insensitive comparison which led to marking a member as
both direct and indirect (in a test case no less).
This patch fixes the comparison and the test.
rob
From c03329d6ea7b5ddda917bca64a6f085efe9e6a95 Mon Sep
