Francois Gouget <fgouget(a)free.fr> writes:
Yeah, maybe a very generic 'Needs review' email to wine-devel would be enough. It would also be the clue to the other Wine developpers: * that you're not going to be duplicating Alexandre's work if you review this patch * to look at the patch, dissect it to see what is wrong * if it is in your domain of competence and it looks good, post an approval message * to test the patch * and help its author get it accepted
That should really be the default behavior, all patches need review; there's no reason to wait until I have looked at a patch to look at it. If you see a patch in an area that you know anything about, please review it, don't wait to see my reaction first. -- Alexandre Julliard julliard(a)winehq.org