From: Brad Smith <brad@comstyle.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Anthony Liguori <aliguori@amazon.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] Fix QEMU build on OpenBSD on x86 archs
Date: Sun, 26 Jan 2014 16:40:18 -0500 [thread overview]
Message-ID: <52E580C2.4020307@comstyle.com> (raw)
In-Reply-To: <52E54EA6.40909@redhat.com>
On 26/01/14 1:06 PM, Paolo Bonzini wrote:
> Il 26/01/2014 02:37, Brad Smith ha scritto:
>>>>
>>>
>>> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>>
>> Is there some sort of process I am missing to have build fixes
>> commited so that QEMU actually builds?
>
> Right now we have problems getting patches committed at all.
>
> This patch and the other NetBSD patch is not lost.
I know it is not literally lost.
I don't follow the list that closely.. what was the reason
for there being two incidents over the last 2 months of there
being no commits for over a week (at least from the perspective
of git.qemu.org)?
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2014-01-26 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 0:49 [Qemu-devel] [PATCH v3] Fix QEMU build on OpenBSD on x86 archs Brad Smith
2013-12-15 4:27 ` Brad Smith
2013-12-20 11:19 ` Brad Smith
2014-01-14 19:08 ` Brad Smith
2014-01-02 7:55 ` Stefan Hajnoczi
2014-01-26 1:37 ` Brad Smith
2014-01-26 18:06 ` Paolo Bonzini
2014-01-26 21:40 ` Brad Smith [this message]
2014-01-26 22:12 ` Anthony Liguori
2014-01-26 23:04 ` Brad Smith
2014-02-16 22:00 ` Brad Smith
2014-02-17 16:20 ` Peter Maydell
2014-02-18 0:36 ` Brad Smith
2014-02-18 9:45 ` Peter Maydell
2014-02-18 18:02 ` Brad Smith
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=52E580C2.4020307@comstyle.com \
--to=brad@comstyle.com \
--cc=aliguori@amazon.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.