Ben Klein wrote:
Unless someone wants to donate an AM2/DDR2 motherboard to me, someone
is going to have to take over the packaging of Debian Stable, Testing
and Unstable packages.
Sure. Send me a newegg link and an address.
~Nate
Alexandre Julliard wrote:
Octavian Voicu writes:
Hello,
I'm trying to compile wine with --enable-maintainer-mode and I get
lots of errors like `ignoring return value of ‘xxx’, declared with
attribute warn_unused_result'. I would like to submit a few patches to
fix them.
Please don't
James McKenzie wrote:
James Hawkins wrote:
On Thu, Jan 14, 2010 at 6:19 PM, James McKenzie
wrote:
All:
Is there documentation anywhere on how to use the TRACE command?
I am trying to print out the contents of a UNICODE string using this commnd.
Thank you.
There are
Anything I can do to help move this along?
~Nate
James Hawkins wrote:
On Mon, Jan 4, 2010 at 7:05 AM, Nate Gallaher wrote:
James Hawkins wrote:
On Sat, Jan 2, 2010 at 10:36 AM, Nathan Gallaher
wrote:
+struct cond_mem {
+struct list entry;
+void *ptr;
+};
+
+static void cond_free( void *info, void *ptr
James Hawkins wrote:
On Sat, Jan 2, 2010 at 10:36 AM, Nathan Gallaher
wrote:
+struct cond_mem {
+struct list entry;
+void *ptr;
+};
+
+static void cond_free( void *info, void *ptr )
+{
+COND_input *cond = (COND_input*) info;
+struct cond_mem *mem, *safety;
+
+LIS
I should have mentioned in the commit message that this approach took
heavy inspiration from the solution to the same problem in sql.y.
Austin English wrote:
Dan and I discussed it, and figured renaming the hardware to reflect
the architecture would be more descriptive:
Macintosh -> ppc32
PC -> x86
PC-x86-64 -> x86-64
sun -> sparc
How does that sound?
+1 here.
Sounds like a solid idea.
~Nate Gallaher
Ken Thomases wrote:
One important reason to avoid whitespace-only changes is it makes git-blame
essentially useless for finding the real source of functional changes.
But is that really important? git-bisect would put you on the other
side of any whitespace changes, and a prudent bug-hunter
Nikolay Sivov wrote:
or should I just fix the
one function I'm planning on touching? Or should I grit my teeth
and ignore the style issues
entirely?
Yes, in most cases. If you plan to rework the whole file with
functional patches feel free to touch
formatting a bit. The common rule is to pre
I'm looking at working on a new area of wine (for me) and the file I'm
going to be working
with is rife with whitespace issues. Literal tabs are sprinkled around
and the 80-col limit
has been broken badly and often in easily fixable ways. I'm wondering
what the acceptable
approach is to these
There's a new patch tracker?
~Nate
Alexandre Julliard wrote:
Folks,
I'll be out for the rest of the week, so there won't be a release this
Friday. 1.1.34 will be released on December 4. And with the new patch
tracker you can watch the patches pile up while I'm away ;-)
I would just like to second Vincent's suggestion.
Vincent Povirk wrote:
It also seems to me that a --disable-gecko-downloader configure switch
that would disable the dialog COMPLETELY (even "when needed") would
put gecko on equal footing with optional library requirements. It
would mean:
* You c
13 matches
Mail list logo
