git & sharing patches (was: SoC idea: improve dsound/winmm)
mike at plan99.net
Sat Apr 22 11:02:52 CDT 2006
I don't know. I simply reverse all my patches before doing a git
update. It doesn't seem able to cope with the idea of non-committed
patches at all. I guess there is probably some way to do it ... maybe
just committing it to your tree will work.
For now I'd just apply it and see if it works. It's a useful data
point even if you don't keep it. We need to get a picture of what
problems are due to faults/data corruptions inside DirectSound/WinMM
itself and what are to do with scheduling.
On 4/22/06, Molle Bestefich <molle.bestefich at gmail.com> wrote:
> Mike Hearn wrote:
> > Do the artifacts change or disappear if you use my thread priority patch?
> I'd like to try out your patch with a couple of apps where sound is shoddy.
> What's the correct GIT way to apply your patch (and still be able to
> pull changes from the Wine tree)?
> Apologies if it's a stupid question, but git --help seems to give a
> plethora of commands and I've absolutely no idea which are meant for
> common use and which are completely useless or will corrupt my local
More information about the wine-devel