<br><br><b><i>Dan Kegel <dank@kegel.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">Dan Kegel wrote <br><br>>Joeseph wrote:<br>>> Is there a Git Repositories for Unaccept Patches or (work >in Progress)?<br><br><br>>Not really, but people often attach patches to bugzilla<br>>entries if they're not quite good enough to submit.<br>>And if anybody wants to start such a git repository,<br>>more power to them.<br><br>Thank I did not know that.<br><br>>>An ntoskrnl.exe was written a couple of years ago to load drivers,<br>>>specifically the Safedisc Windows kernel driver,<br>>> but it still hasn't been accepted.<br><br>>>The article you read is out of date; ntoskrnl.exe is now part >>of >wine.<br><br>This is good to here to.<br><br>>> Basically threat unaccepted patch as bugs(while keeping >>the patch out of wine),
instead of chucking it out the window.<br><br>>As I said above, developers are free to attach patches to bug >reports.<br><br>>What you're really trying to get at is: sometimes developers<br>>get discouraged at how hard it is to get patches into Wine.<br>>But no mechanical aid will really help there. The only cure<br>>is persistance on the part of the developer, and assistance<br>>(chiefly good feedback) from other Wine developers.<br>>After a developer gets a few patches committed, the<br>>wine process starts to feel a lot smoother.<br><br>That basically what i said yes but, the main reason I wanted the git Repositories was it more an acknowledge that you did do something and set a flag developer could use to help people if they wanted to. <br><br>Please don't take this the wrong way but,<br><br> Set a patch that was rejected as a bug report seem to be a round about way of doing thing and a little air-i-gent to me is it not to
you? <br> <br>If this is the way thing are done, why is it not listed in the doc on found on winehq site, or was it there and I missed it.<br><br>Thank Dan you where a big help.<br><br><pre><tt><tt><tt><tt>James Hawkins wrote:</tt></tt></tt></tt> <br><tt><tt>>><br>>> And anyone can publish GIT repos, there is problem with that.<br>>> (And <a target="_blank" href="http://repos.cz/"><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" class="yshortcuts" id="lw_1202692030_3">repos.cz</span></a> (?) has several of them already.)<br>>><br><br><a target="_blank" href="http://wiki.winehq.org/GIT_Repositories"><span class="yshortcuts" id="lw_1202692030_4">> http://wiki.winehq.org/GIT_Repositories</span></a><br><br>>-- <br>>James Hawkins<br><br>I never said you should allow everybody access
<br>just those who sud-met-ted a fairly good patch <br><br>I never saw that site thou,(what is Thank for the tip.<br>I browsed the wiki several times. I never <br>really saw it as hack and i be-leave that why <br>i missed it.<br><br>Thanks.<br><br><br></tt></tt></pre><br><br><br>- Dan<br><br>-- <br>Wine for Windows ISVs: http://kegel.com/wine/isv<br></blockquote><br><p> 
<hr size=1>Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. <a href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ "> Try it now.</a>