From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] some patches for qemu for pkgsrc, DragonFly, NetBSD, HOST_PPC, without POSIX AIO, and more
Date: Fri, 30 Nov 2007 21:45:18 +0000 [thread overview]
Message-ID: <200711302145.19762.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580711301154r6e710205y80fa5dde780b5a88@mail.gmail.com>
On Friday 30 November 2007, Blue Swirl wrote:
> On 11/30/07, Jeremy C. Reed <reed@reedmedia.net> wrote:
> > On Fri, 30 Nov 2007, Jeremy C. Reed wrote:
> > > The pkgsrc build system has several patches against qemu 0.9.0.
> > >
> > > They are at:
> > >
> > > http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/emulators/qemu/patches/
> > >
> > > Do you want them submitted in a certain way?
>
> Unified diff from top level, unrelated changes preferably in separate
> patches?
And with a proper description of exactly what it's fixing and why it should be
fixed that way.
Paul
prev parent reply other threads:[~2007-11-30 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 16:40 [Qemu-devel] some patches for qemu for pkgsrc, DragonFly, NetBSD, HOST_PPC, without POSIX AIO, and more Jeremy C. Reed
2007-11-30 17:33 ` Jeremy C. Reed
2007-11-30 19:54 ` Blue Swirl
2007-11-30 21:45 ` Paul Brook [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=200711302145.19762.paul@codesourcery.com \
--to=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 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.