qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OpenBSD build fixes
Date: Mon, 5 Oct 2009 21:57:50 +0100	[thread overview]
Message-ID: <20091005205750.GA29185@miranda.arrow> (raw)
In-Reply-To: <20091005201628.GP25308@overdrive.home.tratt.net>

On Mon, Oct 05, 2009 at 09:16:28PM +0100, Laurence Tratt wrote:
> It would be good if we could get these patches into the mainline qemu. From
> here, there are a couple of more obviously OpenBSD-only patches that aren't
> suitable for the main qemu tree, and will need to be maintained seperately.

Aren't suitable for the main QEMU tree?  Why?

Is it somehow a *good* thing for upstream releases not to work OOTB under
the BSDs?  I really don't understand this...

(Or is the name "ports" being taken too literally?)

Cheers,
-- 
Stuart Brady

  reply	other threads:[~2009-10-05 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 20:16 [Qemu-devel] OpenBSD build fixes Laurence Tratt
2009-10-05 20:57 ` Stuart Brady [this message]
2009-10-05 21:23   ` Laurence Tratt
2009-10-06 19:33     ` Stuart Brady

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=20091005205750.GA29185@miranda.arrow \
    --to=sdbrady@ntlworld.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).