From: Ben Taylor <sol10x86@cox.net>
To: qemu-devel@nongnu.org
Cc: Christopher Olsen <cwolsen@domainatlantic.com>
Subject: Re: [Qemu-devel] FreeBSD Support
Date: Mon, 19 Feb 2007 21:08:52 -0500 [thread overview]
Message-ID: <20894890.1171937332995.JavaMail.root@eastrmwml08.mgt.cox.net> (raw)
---- Christopher Olsen <cwolsen@domainatlantic.com> wrote:
> This is a sidetrack here... But is it at all possible to make future releases
> of the source more FreeBSD friendly?
>
> I am willing to work off a specified codebase to bring it up to FreeBSD speed
> so it can be easily maintained from there...
>
> Because unfortunately out of the box it doesn't build.
Having been in your shoes, the only thing I can tell you is start
small. Be able to justify your patches and change as little as
possible. Be smart about how you code things if there are
specific reasons. And get ready for a long haul. Be ready to
constantly be porting your changes through the CVS tree.
I can tell you that you won't be able to submit a
"This patch makes it work with FreeBSD"
and have it accepted.
Start with the configure script and Makefiles, and any very specfic, targeted
and small patches and let those changes slowly propogate out.
HTH,
Ben
next reply other threads:[~2007-02-20 2:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 2:08 Ben Taylor [this message]
2007-02-20 2:15 ` [Qemu-devel] FreeBSD Support Christopher Olsen
2007-02-20 5:14 ` M. Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2007-02-16 19:02 [Qemu-devel] QEMU: VNC Christopher Olsen
2007-02-20 0:45 ` Anthony Liguori
2007-02-20 1:05 ` Daniel P. Berrange
2007-02-20 1:15 ` [Qemu-devel] FreeBSD Support Christopher Olsen
2007-02-20 1:46 ` Paul Brook
2007-02-20 2:10 ` Christopher Olsen
2007-02-20 2:41 ` Paul Brook
2007-02-20 3:26 ` Christopher Olsen
2007-02-24 19:08 ` Juergen Lock
2007-02-24 20:54 ` Leonardo Reiter
2007-02-26 0:12 ` andrzej zaborowski
2007-03-03 22:12 ` Thiemo Seufer
2007-03-05 7:38 ` andrzej zaborowski
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=20894890.1171937332995.JavaMail.root@eastrmwml08.mgt.cox.net \
--to=sol10x86@cox.net \
--cc=cwolsen@domainatlantic.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).