comparison ChangeLog.API @ 28449:9e8d0537d37d

I don't think the comment made sense, this is probably what it meant to be. It's only checking status type but not the status message, so it can match the "wrong" status if you have substatuses of different messages. I am not sure if that's a feature or bug though. Seems like a bug to me because it prevents you from setting certain messages if you already have similar transient status. Oh, and why does this matching only work on transient statuses anyway.
author Ka-Hing Cheung <khc@hxbc.us>
date Mon, 26 Oct 2009 06:53:35 +0000
parents 31ff586b8ddc
children 850f1e5491b2 7819d3819f4c
comparison
equal deleted inserted replaced
28448:a5b8f6f2b112 28449:9e8d0537d37d