From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gray Remlin <gryrmln@gmail.com>
Date: Sat, 21 Apr 2012 22:55:56 +0100
Subject: [U-Boot] 'run' no longer aborts on an error,
	can someone please verify
In-Reply-To: <20120421205158.67291204A81@gemini.denx.de>
References: <20120421205158.67291204A81@gemini.denx.de>
Message-ID: <4F932CEC.30808@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

U-Boot v2012.04

Marvell>> setenv ipaddr '192.168.1.130'
Marvell>> setenv ifhostisup 'ping 192.168.1.100'
Marvell>> setenv saywearehappy 'echo "We are happy!"'
Marvell>> run ifhostisup saywearehappy;
Using egiga0 device
ping failed; host 192.168.1.100 is not alive
"We are happy!"
Marvell>> 

This is not the same behaviour as my (unfortunately customised) version based on the ancient U-Boot 2009.11
Other commands are also effected, for example 'ide dev 0' would abort a 'run' command if the device did not exist.

Is this my problem (corrupted source\compilation) or a change in policy ?