Not sure how this bug number made it into the commit log, but the last message is incorrect -- it should point to bug 882933 instead.
Sorry folks!
Not sure how this bug number made it into the commit log, but the last message is incorrect -- it should point to bug 882933 instead.
Sorry folks!