http://bugs.winehq.org/show_bug.cgi?id=17294
--- Comment #9 from Austin English austinenglish@gmail.com 2009-03-01 12:44:36 --- (In reply to comment #8)
OK, apologies if that wasn't the preferred procedure. But I did want to be sure people realized that this bug appears to affect 1.1.16.
Just a simple note "Still present in 1.1.16." is good.
I had thought that if the "version" setting remained at 1.1.14 (the original value), the bug report might end up being ignored because it no longer applied to the current version. Is this, in fact, not anything to worry about?
No, no need to worry.
Or should I submit a brand-new bug report now, citing version 1.1.16?
No...if that were the case, we'd have tenfold the bug reports we already have.