From: "Blue Swirl" <blauwirbel@gmail.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH, RFT] Update i386-dis.c from binutils 2.17 + commits before GPLv3 switch
Date: Sun, 2 Nov 2008 09:35:15 +0200 [thread overview]
Message-ID: <f43fc5580811020035nadf3fa0qaa2e62325b6af281@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
Hi,
The first patch is unchanged, it updates i386-dis.c using binutils 2.17.
The second patch updates i386-dis.c again using binutils files from
CVS: include/opcode/i386.h r1.78 and opcodes/i386-dis.c r1.126. These
are the last versions using GPL v2+. Maybe there are some significant
changes, but I can't find them because of the huge code shuffling.
[-- Attachment #2: update_i386_dis_binutils_2.17.diff.bz2 --]
[-- Type: application/x-bzip2, Size: 15117 bytes --]
[-- Attachment #3: update_i386_dis_last_gplv2.diff.bz2 --]
[-- Type: application/x-bzip2, Size: 23867 bytes --]
reply other threads:[~2008-11-02 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f43fc5580811020035nadf3fa0qaa2e62325b6af281@mail.gmail.com \
--to=blauwirbel@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).