Comment 7 for bug 800527

Revision history for this message
Jeremy Kerr (jk-ozlabs) wrote :

I can confirm that the current git HEAD (4419a4ff8) does not produce this warning. Do you need further verification though?