From: "Blue Swirl" <blauwirbel@gmail.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] struct iovec compilation fix
Date: Sat, 6 Dec 2008 22:20:12 +0200 [thread overview]
Message-ID: <f43fc5580812061220r39ef9cd4i656f5ba76d36c461@mail.gmail.com> (raw)
In-Reply-To: <D8A36573-ADBF-4930-8AB5-457079E9D7BB@web.de>
On 12/6/08, Andreas Färber <andreas.faerber@web.de> wrote:
>
> Am 06.12.2008 um 20:53 schrieb Blue Swirl:
>
>
>
> > On 12/6/08, Andreas Färber <andreas.faerber@web.de> wrote:
> >
> > > The configure test for struct iovec #includes <sys/uio.h> but
> qemu-common.h
> > > did not.
> > >
> > > This fixes compilation of hw/virtio.h on Mac OS X.
> > >
> > > Signed-off-by: Andreas Faerber <andreas.faerber@web.de>
> > >
> >
> > Thanks, applied.
> >
>
> Thanks, Blue.
>
> You're making me wonder, isn't actually the subject line (following
> "[PATCH]") of a Git-style patch supposed to be part of (i.e., the first line
> of) the SVN commit message? Or is that a misunderstanding on my part?
> Noticed that for r5885ff as well.
I don't know. Sometimes the subject does not tell much or there is a
lot of extra garbage. Not in this case, though.
prev parent reply other threads:[~2008-12-06 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 20:05 [Qemu-devel] [5889] Make struct iovec universally available Anthony Liguori
2008-12-06 10:30 ` Andreas Färber
2008-12-06 10:39 ` Andreas Färber
2008-12-06 11:12 ` [Qemu-devel] [PATCH] struct iovec compilation fix Andreas Färber
2008-12-06 19:53 ` Blue Swirl
2008-12-06 20:07 ` Andreas Färber
2008-12-06 20:20 ` 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=f43fc5580812061220r39ef9cd4i656f5ba76d36c461@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=andreas.faerber@web.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).