<br><br><div class="gmail_quote">2009/4/18 vitamin <span dir="ltr"><<a href="mailto:wineforum-user@winehq.org" target="_blank">wineforum-user@winehq.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
James Huk wrote:<br>
> Can I somehow- using git - fetch all patches from date x, for custom dll?<br>
<br>
</div>That's exactly what git does. You literally cloning the entire repository all patches since day 1.<br>
<div><br>
<br>
James Huk wrote:<br>
> I mean can I get all patches from wine-0.9.15 onward for dsound.dll? If so, will I be able to apply them for wine-0.9.15 source?<br>
<br>
</div>No. There were lots of wholesale changes in Wine source tree. You can't backport big changes to each individual dll, especially if it relies on lots of other things.<br>
<br>
<br>
<br>
<br>
<br>
</blockquote><div>�</div>I see. I tried again with:<br><br>git bisect start<br>git bisect good wine-0.9.15<br>git bisect bad<br><br>and... well:<br><br>1st compilation successful - bug present<br>2nd compilation successful - bug present<br>
3th compilation successful - well now even winecfg doesn't want to start � some kind of �can't create window� error (sorry I didn't write it down). Now I tried again with git bisect bad and recompilation � but wine was never able to create window. Few compilations later it failed to compile at all.<br>
<br>My questions are:<br><br>1.Is there a way to compile and test wine using above git bisect?<br>2.If I found regression between 0.9.15 and 0.9.16 � should I report it at all? This is after all very old wine version...<br>
<br>Thank You<br></div>