From: Kevin Wolf <kwolf@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/2] qcow2: Move BlockDriver definiton to the end of the file
Date: Fri, 07 May 2010 18:41:19 +0200 [thread overview]
Message-ID: <4BE442AF.20807@redhat.com> (raw)
In-Reply-To: <h2lf43fc5581005070845t634dcf52w53593417e55b02f8@mail.gmail.com>
Am 07.05.2010 17:45, schrieb Blue Swirl:
> On 5/7/10, Kevin Wolf <kwolf@redhat.com> wrote:
>> A recent build fix for OpenBSD moved the BlockDriver definition of qcow2 to
>> somewhere in the middle of the source file. This series tries to solve the
>> problem in a different way that allows the definition to stay where everyone
>> looks for it.
>>
>> Blue Swirl, as I don't have an OpenBSD installation handy, can you try if this
>> works for you?
>
> Seems to work. Should I commit them or do you want to use the block branch?
I don't mind. It's already in the block branch, so it would be part of
my next pull request anyway. If you commit it before that, that's no
problem either.
Kevin
next prev parent reply other threads:[~2010-05-07 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 10:43 [Qemu-devel] [PATCH 0/2] qcow2: Move BlockDriver definiton to the end of the file Kevin Wolf
2010-05-07 10:43 ` [Qemu-devel] [PATCH 1/2] Revert "Fix OpenBSD build" Kevin Wolf
2010-05-07 10:43 ` [Qemu-devel] [PATCH 2/2] qcow2: Remove static forward declaration Kevin Wolf
2010-05-07 15:45 ` [Qemu-devel] Re: [PATCH 0/2] qcow2: Move BlockDriver definiton to the end of the file Blue Swirl
2010-05-07 16:41 ` Kevin Wolf [this message]
2010-05-07 17:15 ` Blue Swirl
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=4BE442AF.20807@redhat.com \
--to=kwolf@redhat.com \
--cc=blauwirbel@gmail.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 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.