Hi Jeff,
I don't know if I can do all the development work,
because it sounds really difficult.
I want to run a particular application called
WEB.de SMARTSURFER. It's a dialer to get
the cheapest internet connection (in Germany).
Where I live I have DSL, but not when I visit my relatives.
There
Hi Jeff,
I don't know if I can do all the development work,
because it sounds really difficult.
I want to run a particular application called
WEB.de SMARTSURFER. It's a dialer to get
the cheapest internet connection (in Germany).
Where I live I have DSL, but not when I visit my relatives.
There
Hi,
After seeing Gerald Pfeifer's patch, I decided to see how many asserts
were used in wine.
$ find . -type f -iname *.c -exec grep -H assert '{}' \; assert1.log
This returns 2313 matching lines, some of which are including assert.h.
$ cat assert1.log | sed -e 's/:.*//' | sort | uniq -c |
On 03/07/2010 04:38 AM, Reece Dunn wrote:
As a general principle, assert in:
1/ tests should be changed to an ok and possibly a skip --
otherwise, the test results are reported as a crash, making it harder
to find out where the problem is.
+1 In most cases they check for something that
What a morning...
git clone appears to not be working, receiving the old Fatal: Other
end hung up message.
James McKenzie
James McKenzie wrote:
What a morning...
git clone appears to not be working, receiving the old Fatal: Other
end hung up message.
Bad command line and I feel like a I10dt today
James McKenzie
James McKenzie wrote:
What a morning...
git clone appears to not be working, receiving the old Fatal: Other
end hung up message.
Bad command line and I feel like a I10dt today
James McKenzie
Alright, after reviewing everything, I think that tying appinstall into
test.winehq.org along with adding more (if not most) of the wpkg scripts to
appinstall would be most beneficial in terms of conformance and regression
testing. Converting the wpkg scripts to appinstall doesn't seem like that
