Is there a Git Repositories for Unaccept Patches or (work in Progress)?
dank at kegel.com
Sun Feb 10 12:55:28 CST 2008
> Is there a Git Repositories for Unaccept Patches or (work in Progress)?
Not really, but people often attach patches to bugzilla
entries if they're not quite good enough to submit.
And if anybody wants to start such a git repository,
more power to them.
>An ntoskrnl.exe was written a couple of years ago to load drivers,
>specifically the Safedisc Windows kernel driver,
> but it still hasn't been accepted.
The article you read is out of date; ntoskrnl.exe is now part of wine.
> Basically threat unaccepted patch as bugs(while keeping the patch out of wine), instead of chucking it out the window.
As I said above, developers are free to attach patches to bug reports.
What you're really trying to get at is: sometimes developers
get discouraged at how hard it is to get patches into Wine.
But no mechanical aid will really help there. The only cure
is persistance on the part of the developer, and assistance
(chiefly good feedback) from other Wine developers.
After a developer gets a few patches committed, the
wine process starts to feel a lot smoother.
Wine for Windows ISVs: http://kegel.com/wine/isv
More information about the wine-devel