Vincent Povirk wrote:
On Sun, Apr 12, 2009 at 3:05 PM, Vitaliy Margolen wine-devel@kievinfo.com wrote:
Ok, but my point is (and I'm not saying we should necessarily do this), according to the Wine Developer's Guide an err is something that we should be concerned about, by definition. If we buy this, and some current err messages are often harmless, implying no loss of important functionality, they should be changed to some other channel.
+1. If the report is not an error which will cause problems then it should be something else, like a Warning that your program may not function in the way you expect or a fixme, with a note that the requested function is not implemented. There are way to many error messages that are causing concerns with our users.
James McKenzie