Comment 3 for bug 639727

@Rico: PS, I see you put a comment for the new code for 1638 to indicate it is a bug fix - in cases like this you should put the bug number as well in 2 yrs when we see this code and go 'wtf??' we can look up more info easily. ;-)