From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:53992)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Rp8xi-0001g5-GY
	for qemu-devel@nongnu.org; Sun, 22 Jan 2012 20:44:47 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Rp8xh-0005U4-9e
	for qemu-devel@nongnu.org; Sun, 22 Jan 2012 20:44:46 -0500
Received: from mail-gy0-f173.google.com ([209.85.160.173]:57829)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Rp8xh-0005Tu-77
	for qemu-devel@nongnu.org; Sun, 22 Jan 2012 20:44:45 -0500
Received: by ghbg20 with SMTP id g20so1295465ghb.4
	for <qemu-devel@nongnu.org>; Sun, 22 Jan 2012 17:44:44 -0800 (PST)
Message-ID: <4F1CBB88.9040806@codemonkey.ws>
Date: Sun, 22 Jan 2012 19:44:40 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <4F1B0C3E.20905@landley.net> <4F1BB581.6030703@weilnetz.de>
	<4F1C9EF5.9090105@landley.net>
In-Reply-To: <4F1C9EF5.9090105@landley.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Commit 5632ae46 broke the network on mips.
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Rob Landley <rob@landley.net>
Cc: Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>

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 <aliguori@us.ibm.com>
Date:   Thu Dec 1 14:04:21 2011 -0600

     Update version for 1.0 release

     Signed-off-by: Anthony Liguori <aliguori@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
>