On 01/22/2012 05:42 PM, Rob Landley wrote:
On 01/22/2012 01:06 AM, Stefan Weil wrote:
This was fixed with commits e9b40fd34ceb23461083d505a444a389c094455b
and 0b23c5d40ea933cfece3b4f69427f79c8a23256d in master and stable-1.0.
The git tag for v1.0 does not include that commit. Apparently the
current 1.0 tarball on the website does,
Hi Rob,
I've verified this three different ways.. You must have something messed up on
your end.
v1.0 tag is:
commit 1c8a881daaca6fe0646a425b0970fb3ad25f6732
Author: Anthony Liguori <aligu...@us.ibm.com>
Date: Thu Dec 1 14:04:21 2011 -0600
Update version for 1.0 release
Signed-off-by: Anthony Liguori <aligu...@us.ibm.com>
I've verified this locally and on qemu.org.
md5sum of the tarball is:
a64b36067a191451323b0d34ebb44954 qemu-1.0.tar.gz
I've verified that the contents of this tarball match exactly the above commit
after the following commands:
$ git submodule update --init
$ rm -rf .git roms/*/.git
which is odd since e9b4 was
only applied to the git tree _after_ a January 6th commit. So either
"git log" is being weird, or you guys retroactively re-released the 1.0
tarball without renumbering it?
I'm confused...
You somehow messed up your repository or have a bogus 1.0 tarball. Please
confirm the md5sum.
My latest QEMU works with MIPS Malta running from an NFS root.
I can confirm that current -master works for me.
The 1.0 tarball includes the fix, the 1.0 git tag doesn't. I'll include
a note to that effect in my release notes.
That's definitely not the case.
Regards,
Anthony Liguori
Thanks,
Rob