From: "Christian MICHON" <christian.michon@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] current qemu cvs broken for mingw hosts
Date: Wed, 31 Jan 2007 00:13:47 +0100 [thread overview]
Message-ID: <46d6db660701301513t2debe9dfpe4517fe0c72cb11e@mail.gmail.com> (raw)
In-Reply-To: <200701302255.26377.paul@codesourcery.com>
On 1/30/07, Paul Brook <paul@codesourcery.com> wrote:
> Did you test it? I'm fairly certain it still won't work. AFAICS You're not
> setting the field anywhere.
>
it solved the compilation, which was broken, which was my primary
concern. Your patches normally don't break the build :)
so in a sense, with regards to the current cvs state, it helps fixing
the compilation, without segfault for example.
the binary works. The struct statement was missing the "chr".
Now, in term of functionality, I do not know how you test it,
if this was your question.
--
Christian
next prev parent reply other threads:[~2007-01-30 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 19:12 [Qemu-devel] current qemu cvs broken for mingw hosts Christian MICHON
2007-01-30 19:28 ` Johannes Schindelin
2007-01-30 20:09 ` Christian MICHON
2007-01-30 22:55 ` Paul Brook
2007-01-30 23:09 ` Johannes Schindelin
2007-01-30 23:13 ` Christian MICHON [this message]
2007-01-31 16:24 ` Johannes Schindelin
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=46d6db660701301513t2debe9dfpe4517fe0c72cb11e@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=paul@codesourcery.com \
--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).