On 8/27/07, Wolfgang Denk wd@denx.de wrote:
In message 20070827150751.109ac984@dhcp-255-175.norway.atmel.com you wrote:
W0FkZGluZyB1LWJvb3QtdXNlcnMgdG8gQ2NdCgpPbiBNb24sIDIwIEF1ZyAyMDA3IDE5OjAwOjAx ICswMzAwClNlbWloIEhhemFyIDxzZW1paC5oYXphckBpbmRlZmlhLmNvbT4gd3JvdGU6Cgo+IFNp Z25lZC1vZmYtYnk6IFNlbWloIEhhemFyIDxzZW1paC5oYXphckBpbmRlZmlhLmNvbT4KPiAtLS0K
...
Please post plain text only.
Argh...wonder how that happened. Claws Mail claims that it sent plain text, or at least something close:
Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
but after receiving it through the list, that somehow got turned into
Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64
I guess something on the way decided that quoted-printable is unacceptable and turned it into base64...
and below is the fix. Any reason why sha1.c includes <linux/string.h> instead of just <string.h>?
Because there is no "include/string.h" in U-Boot.
But there's usually a /usr/include/string.h installed with the host toolchain, no?
Haavard