From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Update disassembler files from latest binutils
Date: Mon, 27 Oct 2008 10:54:28 +0200 [thread overview]
Message-ID: <761ea48b0810270154x2c7c606es13209e2481471b79@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580810250056g2942594ke98c62958ecc5ad1@mail.gmail.com>
On Sat, Oct 25, 2008 at 9:56 AM, Blue Swirl <blauwirbel@gmail.com> wrote:
>
>> GPLv3 is not acceptable for qemu, which contains v2 only code.
>
> We could update once to binutils 2.17 which is GPL v2+. For Sparc this
> would be about OK, since there is just one commit after GPLv3 switch.
> But for i386 this would mean missing 30 to 50 commits.
I took a quick look at binutils CVS repository: 2.17 released happened
in June '06.
According to ChangeLog, the switch to GPLv3 occured in July '07:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/opcodes/ChangeLog-2007?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=src
So I *guess* getting source out of CVS from June '07 should be safe
license wise, though probably slightly dangerous from a stability point
of view. Perhaps Paul can comment on that?
Laurent
next prev parent reply other threads:[~2008-10-27 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f43fc5580810241101ra7099ddj260f6eb36a2edd35@mail.gmail.com>
2008-10-24 19:12 ` [Qemu-devel] [PATCH, RFC] Update disassembler files from latest binutils Blue Swirl
2008-10-24 19:36 ` Kirill A. Shutemov
2008-10-24 19:46 ` Blue Swirl
2008-10-24 19:38 ` Andreas Färber
2008-10-24 19:59 ` Blue Swirl
2008-10-24 20:05 ` Aurelien Jarno
2008-10-24 20:16 ` Stefan Weil
2008-10-24 23:48 ` Thiemo Seufer
2008-10-24 23:50 ` Thiemo Seufer
2008-10-25 0:06 ` Paul Brook
2008-10-25 7:56 ` Blue Swirl
2008-10-25 10:17 ` Laurent Desnogues
2008-10-27 8:54 ` Laurent Desnogues [this message]
2008-10-27 9:37 ` Laurent Desnogues
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=761ea48b0810270154x2c7c606es13209e2481471b79@mail.gmail.com \
--to=laurent.desnogues@gmail.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).