Hi,
--- Jonathan Wilson jonwil@tpgi.com.au wrote:
And also they are trying to figure out how to make sure that when someone changes the bison files or the .c files generated from them, the changes are copied upstream to WINEHQ and not lost.
Casper has provided a solution that will work. Once we move to subversion and have atomic commits we can create a patch penguin that will dump all of that patches that affect wine modules in to a que that the ReactOS-Wine maintainers can then forward to wine-patches. It wont be fully automated as we don't want to spam wine-patches with ReactOS hacks but good patches can then be reviewed with little hassle and be forwarded. If it works well then I will look at extending it or creating my own CI system that is tied to Winehq cvs.
Thanks Steven
__________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250