Wine patch code review or what to do if patches get stuck?
jwhite at winehq.org
Tue Apr 21 09:18:48 CDT 2009
> Sometimes "no feedback" means that you just dont know - is there
> something wrong? Or maybe your patch wos not understood correctly? Or
> there are doubts that what you did is right? Or what? It would be
> better to have feedback like "are you serious?" than nothing at all :)
I've tried to update the 'why was my patch ignored' section in the Wiki:
to reflect what I understand from Alexandre.
Not sure if any of it applies in your case, but I thought it'd be good
to have it in the mailing list archives.
More information about the wine-devel