Chris Morgan [EMAIL PROTECTED] writes:
the winetest results are sent back to winehq and can be
accessed via http://test.winehq.org/data/ Pretty
formatting of the results is coming soon ;-)
Do you mean somebody's already working on it or that I
should do it eventually? I'm back from the
On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
work again. It would even make more sense now that the dust
settled. Have you perhaps got concrete ideas?
So here is what's left to do:
1. Finish the metadata-in-winetest patch
2. Arrange the reports on WineHQ
3. Maybe add
Am Freitag, 28. Mai 2004 23:59 schrieb Mike Hearn:
On Fri, 28 May 2004 15:59:23 -0500, Alexandre Julliard wrote:
Log message:
Initial version of the Wine preloader, used to reserve memory
areas at startup. Based on the work of Mike McCormack.
[snip]
If you observe any odd
On Fri May 28 23:42:14 BST 2004, you wrote:
Mike Hearn [EMAIL PROTECTED]
Print thread ID in 16-bit snoop traces in the noargs case
Too late:
http://cvs.winehq.org/patch.py?id=12478
Rein.
--
Rein Klazes
[EMAIL PROTECTED]
On Fri, 21 May 2004 12:58 am, Francois Gouget wrote:
On Thu, 20 May 2004, Mike Hearn wrote:
[...]
This is no longer true. According to a Red Hat kernel engineer, you can
use setarch i386 wine to switch it back to the 3/1 split while we
fix it in the Wine code.
Don't we have the
On Sat, 2004-05-29 at 11:49 +0200, Rein Klazes wrote:
Too late:
http://cvs.winehq.org/patch.py?id=12478
Haha :) Golden rule of Wine hacking: before writing a patch, update!
OK, well at least we didn't duplicate anything hard
Alexandre Julliard wrote:
Wililam [EMAIL PROTECTED] writes:
Here is the ChangeLog entry:
* dlls/kernel/lcformat.c
William Lahti [EMAIL PROTECTED]
- Implemented the EnumDateFormatsW function and vastly improved upon the
EnumDateFormatsA function.
This stuff clearly needs to be
Hello this line:
However, disassembling NT implementation (WIN32K.SYS) reveals
that.
in
http://source.winehq.org/source/windows/win.c#L845
was introduced in to winehq by the following patch:
http://cvs.winehq.com/cvsweb/wine/windows/win.c.diff?r1=1.61r2=1.62
Does this not violate a
However, disassembling NT implementation (WIN32K.SYS) reveals
that.
...
Does this not violate a clean rooming the implementation? The ReactOS
code is a derived work of the Wine code in the case and if soon then we
have to remove it.
Whoa! Slow down there John Wayne! Disassembly is
This patch
http://cvs.winehq.org/patch.py?id=12495
seems to have broken the mingw build, currently getting
i386-mingw32msvc-gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
-D_REENTRANT -Wall -pipe -fno-strength-reduce -mpreferred-stack-boundary=2
-fno-strict-aliasing -gstabs+
10 matches
Mail list logo
