From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Moore <moore@free.fr>
Date: Thu, 10 Feb 2011 07:22:09 +0100
Subject: [U-Boot] Thunderbird bug (was PATCH-add "0X" hexadecimal prefix
 to simple_strtoul)
In-Reply-To: <4D5382B0.30708@free.fr>
References: <4D51716D.3060002@motorola.com>	<20110208191447.BFECA14B9A35@gemini.denx.de>	<4D523204.5040105@free.fr>	<4D5236EC.2040703@free.fr>
	<20110209151738.377f32b2@udp111988uds> <4D5382B0.30708@free.fr>
Message-ID: <4D538411.2050805@free.fr>
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

Hi,

Me again.

Le 10/02/2011 07:16, Chris Moore a ?crit :
> Hi,
>
> Le 09/02/2011 22:17, Scott Wood a ?crit :
>> On Wed, 9 Feb 2011 07:40:44 +0100
>> Albert ARIBAUD<albert.aribaud@free.fr>   wrote:
>>
>>> Le 09/02/2011 07:19, Chris Moore a ?crit :
>>>> I also noticed this in some of my (rare) posts.
>>>> I am using TB 3.1.5.
>>>> I am too ashamed to admit my OS ;-)
>>>>
>>>> A nonsense test case written with correct spacing: a = (b>   (c>>   1))&&
>>>> ((d<   ((e&   1)<<   1)));
>>>> If you receive this correctly then please excuse me for the noise :(
>>> Received correctly. :)
>>>
>>> In Rob's case I am not sure that the issue is due to TB eating selected
>>> spaces upon reception; my own TB (3.1.7), using ^U to display the raw
>>> message from Rob, shows missing spaces are actually in what was sent,
>>> and I think Wolfgang does not use TB at all.
>> It's when quoting a message for a reply that Thunderbird does this mangling.
>>
> Right, that would seem to be this bug:
> https://bugzilla.mozilla.org/show_bug.cgi?id=448198
> I have certainly encountered this one when quoting :(
>
> But there is also: https://bugzilla.mozilla.org/show_bug.cgi?id=597181
> I wonder if I haven't run into this one too :(

Note that my reply introduced the quoted text bug in my test case above :(

Cheers,
Chris