[Wine] Re: Call for volunteers

fcmartins wineforum-user at winehq.org
Sat May 9 10:52:53 CDT 2009

Freakazo wrote:
> Ah all right thanks.
> I just chose a random bug (http://bugs.winehq.org/show_bug.cgi?id=14586)
> which installed without problems (though the program still doesn't work). So that bug is fixed, then I added a comment saying that it does.
> Is that how things should be done? Should I add the terminal output when reporting that a bug is fixed or is that only necessary when making a new bug report or confirming that a bug still exists.

Looks fine to me. I don't know what criteria is used by the Wine team (or is it just A. Julliard?) to actually close the bug.
I guess, with a bit of look the next wine release will report this bug as fixed/closed.

> And someone said something about doing a trace like this: winedebug=+relay,+seh,+tid wine setup.exe
> Is that basically just making the debugger more verbose?

Yes, but it should be only relevant when the bug is not fixed.

More information about the wine-users mailing list