From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>,
The OpenBIOS Mailinglist <openbios@openbios.org>
Subject: Re: [Qemu-devel] svn 6658 broke powerpc.
Date: Tue, 24 Mar 2009 21:50:45 -0500 [thread overview]
Message-ID: <49C99C05.6020105@codemonkey.ws> (raw)
In-Reply-To: <49C9994F.2040803@codemonkey.ws>
Anthony Liguori wrote:
> IANAL, but from the FSF GPL FAQ, you just have to make sure the source
> code is available. Since Blue Swirl is an Open BIOS maintainer, I
> think we can say with confidence that the openbios code will always be
> available. If that situation changed for some reason, we'd have to
> mirror their code.
Specifically:
http://www.fsf.org/licensing/licenses/gpl-faq.html#SourceAndBinaryOnDifferentSites
Not too long ago, I went through and attempted to make sure the
instructions in pc-bios/README were very clear how to obtain the sources
for the binaries we ship. Patches are always welcome if people think
they need clarification.
Regards,
Anthony Liguori
> Regards,
>
> Anthony Liguori
>
>
next prev parent reply other threads:[~2009-03-25 2:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:57 [Qemu-devel] svn 6658 broke powerpc Rob Landley
2009-03-18 8:41 ` Alexander Graf
2009-03-18 18:28 ` Rob Landley
2009-03-18 19:11 ` Blue Swirl
2009-03-19 3:16 ` Rob Landley
2009-03-19 17:48 ` Blue Swirl
2009-03-19 19:30 ` Rob Landley
2009-03-19 19:41 ` Blue Swirl
2009-03-21 9:32 ` Blue Swirl
2009-03-21 18:44 ` Rob Landley
2009-03-22 15:14 ` Blue Swirl
2009-03-22 16:54 ` Blue Swirl
2009-03-25 2:30 ` Rob Landley
2009-03-25 2:39 ` Anthony Liguori
2009-03-25 2:50 ` Anthony Liguori [this message]
2009-03-25 4:26 ` M. Warner Losh
2009-03-27 18:59 ` Blue Swirl
2009-03-27 19:41 ` Anthony Liguori
2009-03-28 20:41 ` Rob Landley
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=49C99C05.6020105@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=openbios@openbios.org \
--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).