From: "Hotmail" <computers57@hotmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu Devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] another patch against head
Date: Wed, 28 Nov 2007 09:16:12 -0700 [thread overview]
Message-ID: <BAY133-DAV2D882EB19338F5E6161A6B9770@phx.gbl> (raw)
In-Reply-To: Pine.LNX.4.64.0711281247010.27959@racer.site
----- Original Message -----
From: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
To: "Hotmail" <computers57@hotmail.com>
Cc: "qemu Devel" <qemu-devel@nongnu.org>
Sent: Wednesday, November 28, 2007 5:49 AM
Subject: Re: [Qemu-devel] another patch against head
> Hi Hotmail,
>
Hello. Please call me C.W.
> ...
> > (patch to cocoa.m)
> How does this help compiling on Windows?
It doesn't. It's just a little patch should someone decide to build it on cocoa and are confused
>
> > (patch against monitor.c and hw/adlib.c)
> Why are these needed? It appears that all other platforms build QEmu just
> fine without these #includes.
I also seem to have this problem on my Linux box. It could be my cvs files has become disjoined from the server, or both compilers somehow don't include the needed headers elsewhere in the code.
> But then, the answer to that riddle could be in the context. Since you
> did not use the unified diff format, I have no chance to know.
How would I make a unified diff from a command line?
next prev parent reply other threads:[~2007-11-28 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 19:17 [Qemu-devel] another patch against head Hotmail
2007-11-28 12:49 ` Johannes Schindelin
2007-11-28 13:39 ` Samuel Thibault
2007-11-28 14:01 ` Johannes Schindelin
2007-11-28 14:09 ` Samuel Thibault
2007-11-28 14:34 ` Johannes Schindelin
2007-11-28 16:16 ` Hotmail [this message]
2007-11-28 16:35 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-11-28 17:28 Re : " Sylvain Petreolle
2007-11-30 15:35 ` Hotmail
2007-12-02 17:49 ` Thiemo Seufer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY133-DAV2D882EB19338F5E6161A6B9770@phx.gbl \
--to=computers57@hotmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).