From: Blue Swirl <blauwirbel@gmail.com>
To: Kevin Wolf <kwolf@redhat.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, 7 May 2010 20:15:27 +0300 [thread overview]
Message-ID: <q2mf43fc5581005071015ib51be7f5ncc8e8070ab433d46@mail.gmail.com> (raw)
In-Reply-To: <4BE442AF.20807@redhat.com>
On 5/7/10, Kevin Wolf <kwolf@redhat.com> wrote:
> 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.
I applied them then, thanks.
prev parent reply other threads:[~2010-05-07 17:15 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
2010-05-07 17:15 ` Blue Swirl [this message]
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=q2mf43fc5581005071015ib51be7f5ncc8e8070ab433d46@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=kwolf@redhat.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).